>Thanks,
>
>We have considered the alteratives you mention and have not found a good reaction from our client base for them. We have narrowed it down to staying with VFP as the back-end ( which doesn't make our client base happy, us either really ), allowing a SQL Server/Oracle back-end ( not our choice for cost and over-head reasons ), and using Codebase or dropping our dbc and using free VFP tables and moving all the stored procedures, rules, triggers, and RI to data tier with Stonefield as the meta manager. We also are looking down the road and we are kicking around re-writing our app totally in VC++ ( a small percentage of it already is ). Our clients aren't to worried about the front-end, but are wanting us to change the back.
>
>I have white paper reviews on Codebase, better than SQL, but haven't talked to anyone who actually uses it. Just wondering. We are going to get the free trial and evaluate it I just wanted a head start on it.

After reading all the posts in this thread, one thing comes to mind... what is the underlying reason for the change? I mean are you experiencing problems? Are you/your customers unhappy with performance?

Making a move from VFP to VC++ is a move backwards IMO... if you have a data intensive application, you have the application written in the right language already.

If you are considering SQL Server in the future, then MSDE is the right choice if you want to move away from VFP.