>>Output to a portable reader for downloading a program is generally done through the comm port. Portable readers have their own proprietary programming languages, with few standards, and even fewer meeting the standards.
>
>So, maybe we will end up by using the manufacturer software to download the data into an ASCII file. They have a version of the software which is a Windows interface. So, we can have that utility loaded at the same time the Visual FoxPro application is loaded. A simple switch after the download in the Visual FoxPro application for the import will do the job.
>
>As you said, the manufacturer told us that they were using their own language with special things that it is very difficult to try to do the same thing in an application to avoid the use of their software.
>
>I have a meeting with them in two weeks so I will have more information.


If we must then we will most likely use the MSComm32 library that is included in Windows. The main reasons are we know it will be supported in future versions. Plus since it is ActiveX we can, in the future, use it in any type of app including Intranet/Internet apps.

I have severe concerns with FOpen(), etc in the Win/95,Win/NT environment among others.

The only thing I am concerned about is dynamic input. If a user scans will the data end up in the correct field. I thought I heard Code 39 was good for this.

Any suggestions out there?

Thanks
Tom