>Gary DeWitt did a presentation on this type of application at one of the Great Lakes Great Database Workshops in Milwaukee. If I remember correctly, he used SQL Server on the backend, MSDE on the laptops, and a VFP application that could switch between the 2 databases. When the user was ready to disconnect from the server, the app would use replication to copy the data to the MSDE database. While on the road, the user would update the data on the MSDE database. When the user returned, the app would replicate the data from the MSDE database to the SQL Server database.

I wonder if I can get ahold of that presentation (if it was powerpoint). That would really help me to get into what SQL Server could do for those not fully connected.

Thanks for the info.

By the way I was down your way not too long ago. Our church hired a minister that worked in Cynthiana KY. I sure loved the drive down and the horse farms. Went to Southeast Christian Church for a seminar also. Nice place.

>
>>We are curently working on the next generation of our software here and I have a few questions about data access methods. The wisdom from above will be chosing SQL Server as the database backend. I have worked on nothing but FoxPro for years, so SQL Server will be new to me, but the present VFP System allows the user to use the same executable to run with data from the network and from their local PC. We call it split mode. So when the user undocks their laptop they have the local data to view while they are in a meeting or whatever. When they get back to the office and dock their laptop, then they run a utility that will refresh the local data with what is currently on the network. VFP data and databases have the ability of being very portable even with one table being almost 1.3GB. So my question is if I am told to use SQL Server as the backend, then can a solution that I have just described be created for the user using SQL Server? What would it require on the laptop? I do
>>not think that I am blazing new trail.
>>
>>The over all goal with this new system is to be entirely web based with an SQL Server backend and a to-be-decided middle tool. But I have pointed out that we have people who physically cannot get access to the system via the web. So how can I help them out?