So would the serial port/comm just be to connect to the internet/vpn with a modem? If this is the case, that is pretty much built into dial up networking. You can set up a PC to dial the internet automatically when a browser is opened.

And, if not, why would you do the serial access from the client once you moved to an ASP.Net model? Why not send the data from the client to the web server, and then the web server could do the serial communications.

BOb



>Sorry, I didn't explain myself correctly. I didn't mean we were moving from ASP to ASP.NET, rather we are moving from a conventional VFP / SQL Server application to ASP.NET. We have many reasons to do this, but one minor reason is that it will allow us to host the data in a single location which will ease installation, configuration and support - rather than having separate SQL Servers and VFP applications installed locally in different countries.
>
>That is the target but we have to retain hardware device comms at the client. There is always something that gets in the way <g>.
>
>Regards,
>
>Aaron
>
>>I'm not sure I'm following you. What difference does ASP vs. ASP.Net make? >This is a client side issue that is independent of server software used...
>
>+++ Rick ---
>
>>>Thanks Rick for the response.
>>>
>>>Sadly this is what I feared. One of the reasons we are switching to ASP is to reduce installation problems as we will have 5k+ clients. I guess we are going to have to try and find the best "bad" solution we can come up with.
>>>
>>>Anyway, it was worth a shot in the dark.
>>>
>>>Thanks again.
>>>
>>>Aaron