>One option, but more complicated than just hitting SQL Server is to use queued components. Database updates will be queued on the workstation, then automatically sent to the server when the connection is up and running. This way, you don't have to check that the connection is there. And if it goes down during the database update, it's sent again automatically. To learn about QC, see the COM+ articles on my web site.
>
>>I'm at a point where I'd like to migrate my application from a local VFP database to a remote database (most likely SQL server) with a multi location setup.
>>I'd like to get opinions of what type others would recommend to accomplish this most rapidly and easily.
>>
>>If I were to use remote views to a sql server database, does the remote(over a WAN) transaction work the same as a LAN setup? Is it fast enough to consider?
>>
>>Allen

Thanks. The recommendation is great. I'm going to read your articles.
But, recognizing that I'll need to redesign the complete architecture of my app is what's giving me a pit in my stomach.
Cheers,
Allen