If you are looking to replace the system, consider putting your data into SQL Server and use database subscriptions to replicate data at field offices. Field offices could function regardless of current internet connection status. Depending on database size, Field offices could use SQL 2005 Express on their end to keep costs minimal.

Another SQL server option would be to make the central SQL server available over the internet directly although this would mean clients would not be functional when a connection was down.

Either way you gain reliability and scalability.

>Greetings!
>
>Our client uses a centralized system for maintaining their data. That is, they have a Windows 2003 Server box running Terminal Services. On this box, the VFP databases reside. They have 17 different databases (all have the same tables, structures, etc.), one for each field office. Most of the data entry is done in the coporate office with the exception of 3 remote users, who access the system via an RDC connection via Terminal Services.
>
>We are currently planning a system to replace this centralized processing model. This is necessary since it has been determined that the best entry point for most of the data is in the field locations. This would be simple enough if not for another application that must run locally at the field locations. This is a time clock application that MUST (because of State regulations in some cases) be at the field location.
>
>So, here's the dilemna that we are faced with...
>
>We want to maintain the main databases at the centralized location giving the field locations access via Terminal Services (RDC). However, the time clock application must run locally AND it must use data stored in the MAIN database to validate time entries. It would also be nice if the data could be additionally captured into the main database ASAP.
>
>Keeping in mind, that although we could use web services to technically resolve the issue, if the internet connection goes down, the field location would violate compliance regulations for that state and lose their license.
>
>I have read alot of the postings on UT regarding Terminal Services and I see that some of you have run VFP apps with over 200 simultaneous logins. That's greate! I have also read many of Rich Strahl's whitepapers on the subject of remote/internet access. None of them seem to quite fit what we want to do.
>
>So, what are our options? Any information or even pointing me in the right direction will be greatly appreciated!
>
>Thanks!