We have a client we wrote EDI for that is a public warehouse for dry, cooler and freezer commodities. The are a small client and could not afford those "VAN" fees. Several of their companies require that the VAN transmit to our client and we respond back. It works pretty well and my client customer has to pay those VAN fees and we just use FTP to talk back and forth. My client's other customers all communicate through their own FTP servers.
We have a process that wakes up every 15 minutes and checks for incoming transmissions. Our outbound process is on-demand. All jobs are put in a "queue" and processed via FTP one at a time. We tried several queues but our machine was much faster that theirs and we jammed them up. My client is processing about 500 transactions a day with all of the code written in UniBasic. We have written a 846, 940, 943, 945, and 997 that use flat files incoming and outgoing. There is one caveat. There is really no EDI standard. Each customer has fields they need that are used in replace of the specification or extended on the specification. One field that caught us by surprise is the used a vendor name field and prepended the vendor code on to. So we have to parse it for only that customer. Regards, Doug www.u2logic.com
_______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
