>We are currently in a lull with our development cycle, so I have been given the task of comparing VFP to SQL. We have about 40 tables that get regular use and then another 150 tables for whatever. Our main tables have about 1,000,000 records in them and about 500mb in size. Some in the IS dept. have said that we could triple our data and still be alright. Others think we should upgrade to something like SQL or Oracle. I have been trying to find some stats or performance info to justify staying with FoxPro or to move to a differnet backend. Does anyone know of someplace I can look for the data. If we need to migrate our data, I would rather do it while we have the time instead of when it breaks down. TIA.

John,

As a "FoxPro guy" with some 14 years of making a living as it I'd agree with everything the others have said.

Essentially, a decision like this should be made with the future in mind. Will you be using a WAN? Will everone ALWAYS be on the same network? Do you have needs for multiple "types" of logons, ie. Internet, Intranet, local, etc?

Then there's the third approach that I'm taking with my current development. I'm putting ALL SENSITIVE Client information into SQL 7.0. It will be stored in the SQL tables in an encrypted fashion (multiple credit card numbers for each client, bank account #s, etc) just to be safe. All other non-sensitive data are going to go into the VFP DBC for speed reasons. This would be stuff like user's preferences, report definitions, etc. There's no real reason to stash them into a SQL table yet.

IOW, the VFP DBC gives your the best of both worlds. Your answer doesn't have to be one or the other - it can also be a mix of both.

Best,

DD

Best,

DD