>Simon,
>
>It is great that EPS is willing to share some of these tools with the community. I know these tools take care of various parts of the process and handle the plumbing work. However poeple have to keep in mind that the whole cleint-server world is different and it alters the application design from the ground up. IOW, an application that was designed using VFP as the entire suite of tools is most assuredly is not an optimized design for a client-server approach. It really comes down to taking a single tier monolithic application design and redoing it in a multi-tiered approach.

Very good point, Jim. And a very good reason to do all current VFP development with upsizing in mind. View based applications, designed n-tier upsize very well. At this point, I think a strong case can be made that all new VFP development should be against a SQL (Express) backend. Definitely leaves more options for the future of both the app and the developer. A strong VFP app withe SQL data can be supplemented for web or tricky interface with .net modules or whatever. Best of both worlds.

I've found a tool called FullContact that does a terrific job of mapping VFP data structures to SQL Server tables and converting the data. The mapping persists so it can be tweaked if the structures change on either side. Very pleased with it.

Haven't seen the EPS tool yet, but given the overall skill and experience of Markus and the crew I am sure it is amazing.