><<snip>>
>Another way of doing EDI is like this.
>
>There is a product out there from a company known as supply tech. They will do all of the communications etc. for you. (Software)
>They're software can be setup to work with just about any modem etc.
>
>To send an EDI from Fox, I create a text file with the approipiate structure for import by this program.
>This program processes the EDI.
>
>This is a general description of the way I have set it up, and I am sending EDI's to GM, Chrysler, and other suppliers.
>
>1. Foxpro Polling system collects data for EDI (Actually a bar code data collection system)
>2. Foxpro processes the paperwork for the shippers and creates the EDI at the same time. (Creates text file mentioned above.)
>3. Store resultant EDI text file in a memo field of a table.
>4. Check to see if EDI file exists. (This software, expects the file to have a particular name. Once it sends the EDI it renames the file.)
>5. If file exists.. return to poll.
>6. If file does not exist, copy memo field to file and poll.
>
>The neat thing is the use of the text files. This software can be automated to send EDI's on a schedule basis or right away.. It also will receive the releases and save them in a text file format for direct imports into scheduling etc.
>
>Hope this gives you some ideas,
>
>Mike

In our situation, we are a host, so we wait for data coming to us and we have to process this data and sent it back...the text file approach doesn't work well for us as we have a time constraint with which to deal (ie. we do everything in one program, one language (C++) to process the transaction quickly).

Joe