>>>Could you set up a VFP OLE server on a NT 4.0 box with the DBC and tables local to that server and then provide a UI that communicates with the OLE server over a WAN? At least four tables critical to the legacy Fox 2.6 (DOS) app are each in excess of 200+ megs plus extremely bloated CDX's... How do you handle WAN solutions?
>
>Remote automation - sure. Until Tahoe is released - there is a scaleability issue with VFP servers and web servers - which is something you could do over your WAN. Web Connect - from Rick Strahl is a great tool.
>
>How many remote machines are involved here? If there is a lot - you are going to want to minimize what gets distributed to those machines. Otherwise - it can become a maintance nightmare managing things. Another reason why the web idea is nice.
>
>As Craig suggested, ADO or RDS (Remote Data Services)for that matter - would be a nice idea. ADO is light and very scaleable. The only thing to manage in this case is getting the client portion of ADO installed on the machines - which is not that big a deal. I think if is included in IE 4.

Would 60+ users present a problem with VFP Automation? This could be the next best thing to C/S for my company.

By the way, do you agree with some postings here that VFP requires too many workarounds? If you had to rewrite a legacy FoxPro 2.6 (DOS), would you consider VFP or opt for VB?

Regards,
Jack Mendenhall
RMI