>>Hi guys!
>>I am not sure what happened with the messaged I e-mailed the other day
>>about EDI, but I don't see it being posted here, so, - here I go again :)
>>
>>Has anyone worked with EDI protocols on the communication side? I am
>>pre-releasing a quick'n'dirty 'Double-Sided/Double Entry' EDI full-cycle
>>processing by January 1st. Right now it'll go as is, half in VFP and half
>>in SmartTerm (through DDE). I'll say in advance that I am not ready for
>>that notorious ActiveX that everybody is talking about. But I do need to be
>>able to perform file transfers in compliance with ASC 12/ACS 12.6
>>communication protocols. My ideal solution will be to do it in VFP, without
>>firing DDE conversation or any other conversation for that matter, just use
>>good old OpenComm/ReadComm/WriteComm/CloseComm with all intermediate
>>FlushComm's and such. Can anyone give me a short but exact sequence for all
>>those API's for both Send and Receive procedures? I would greatly
>>appreciate it!
>>
>>
>Quick and dirty, hmmmm. See the MS KB and use the Keywork MSCOMM32 thast
>should find their example for moving characters to and from a serial with
>the serial port OCX. It does work
>
>A quick code fragment reading from port
>
>THISFORM.ioSerialPort1.InBufferSize=20000
>THISFORM.ioSerialPort1.HandShaking=2 && RTS
>
>THISFORM.ioSerialPort1.CommPort = pInputPortNumber && 1 or 2
>THISFORM.ioSerialPort1.Settings = pInputSourceName && "9600,n,8,1"
>THISFORM.ioSerialPort1.InputLen = 1
>THISFORM.ioSerialPort1.ParityReplace = "" && No Parity
>THISFORM.ioSerialPort1.DTREnable = .T.
>THISFORM.ioSerialPort1.PortOpen = .T.
>InputBuffer = ""
>THISFORM.ioSerialPort1.InputLen = IN(MaxBufferSize,CharactersAvailable)
>InputBuffer = InputBuffer + THISFORM.ioSerialPort1.input
> && Get Data Count
>*
>* Much later....
>* Close up shop
>THISFORM.ioSerialPort1.PortOpen = .F.

Mscomm32 will certianly do a good job of serial communications. It does not include any file transfer protocols though. I think the name of the company that wrote it is Crescent systems. They advertise an upgrade version that includes transfer protocols (xmodem,ymodem, etc). EDI is probably beyond the scope of this though. The Help About screen of the control gives you the name of the company. You may want to contact them about and EDI specific .ocx control. We have a group, at work, that does EDI mostly, and I can ask them, after the holidays.

HTH
Glenn