MaxFrame has excellent business and data objects. They would make your VFP app better and make it easier to switch to a SQL Server backend.

>Hi all,
>
>I mentioned previously that my main client would like me to present a proposal in about a month whether they should start moving towards replacing their VFP app over time with "whatever is best". Although I have given my opinion that most likely VFP is going to work fine for them for probably the next decade, since I plan to retire in 5 years, they think it is prudent to start on the road to replacing it while I am around. The app is at the core of their business i.e. NOTHING happens in their business without the app. VFP has been very good to them over the years in that we have been able to automate every department of their business and their staff can now handle about 3 times the volume as they did years ago because of automation (including automating Word and Excel and Adobe templates). So they are asking about the risk of staying with VFP and "doing nothing" until it breaks vs. starting to replace it.
>
>The thought I had (and others have affirmed) is to replace the backend first as generally, the users should not see much difference in how the app functions. So my initial questions are going to be on SQL server.
>
>There are probably 10 times the questions than I can think of so I thought I would throw out the ones that come to mind as a starter but I am open to others just stating their experiences of what they had to re-write when transitioning. Not even sure where to start but there goes:
>
>- is there any type of data that does not match up between VFP and SQL?
>- can all types of queries bring down the same data to VFP i.e. selecting into an array, local cursor etc or do some things need rewriting?
>- does referential integrity need to be handled by the back-end or if the logic is in the front end, can it stay there for now?
>- do the table structures need to change at all e.g. if the table uses a primary key generated from a "keys" table (as the framework I use does), does it have to change to an AUTOINC field etc?
>
>That's enough for now...
>
>Thanks,
>Albert