To work with ActiveX-Controls in VEE :

1. Copy it to any directory (windows default is ..\system (Win98/Me) or ..\sytem32 (NT,XP,2K))
2. right-click the *.ocx -> open with -> ..\regsvr32.exe (in the system dir).
   You'll get the message that the control is registered now.
3. In VEE open Device/ActiveX Control References.. and check the desired control
   ( here 'Sercomm Control ..'). Then there is a new line 'ActiveX control' from 
    where you can put it into your application.
    Step 3 is not needed if you open an existing program which uses this 
    control (f.e. SimpleSerial.vee).
    All the functions and methods you'll get in VEE from 
    Device/Function&ObjectBrowser/ActiveX Objects.
    

To work with SerComm-Control :

1.  Before the first run right-click the control -> Control Properties (NOT          properties !) and set the values needed for your application.
    All what you set there (don't forget 'apply' ) will be stored for this           application and will be there even if you run it again next year.
    You can access 'Help' within 'Control Properties' when the help-file and
    the *.ocx are in the same directory.
        In 'SimpleSerial.vee' probably you only have to change the port and 
    the baudrate. (And don't think about the timeouts. Even in Microsoft's 
    papers there are very different opinions).
    'SimpleSerial.vee' transmits every 0.5s an 'a' to request ADC-readings 
    from a micrcontroller-device.
    With WinXP you can't influence stripping of CR, it's done by the system. 
    
2.  In 'Sercomm1.vee' are added:

    - the port-number is set by a function. This value doesn't overwrite
      the setting in 'Control Properties' and is valid only for this run.
      Try it with different settings !
    - Receive() is triggered by InBufferCount() > 0. It's for optics only
      (to avoid empty lines in 'logging Alphanumeric' when theres nothing 
      to receive after o.5s).
      Receive() will even without that trigger only read the number of bytes 
      in the InBuffer and can't block your system if there's nothing to read.
    - EventHandlers added. To see how it works add a MessageBox (without any           connections) to 'EvRXChar' via 'edit Event Handler' after right-click 
      the control or from VEE's program explorer. Then you'll have to welcome 
      every byte coming in.

3.    I made this control for my needs because the Microsoft MSCOMM32.OCX
      has a bug (licensing under NT,2K,XP).
      Maybe (it's very likely) I forgot something which is important for 
      others .
      -> please give me a feedback if you find a bug or if you have
         proposals to add/change something.   

      Detlef Kersten