>Linos:
>
>The fact that MS packages Access with Office and VFP with Visual Studio say alot.
>
>Charlie

Add to that the fact that *when* you break a table you've just broken *A* table. Since Access stores all of its eggs in one basket (file), so to speak, when you break that you've broken the whole thing.

When I was called in on a VB project that was designed using Access and the main thing I noticed was that as the size of the MSD got above a 200MB the whole app just dropped to a crawl. Getting above 200MB is not hard to do with Access. The other thing I noticed was the instability.

I developed a VFP app here, where I work, that has 125 tables, 80 forms, 20 menus, and 200 reports. I develop hot because of the rapidly changing requirements. You just can't do the 'regular' dev cycle here, the legislature changes the goal posts too often. I doubt that Access could stand up under this environment. I get daily requests for mods that would be impossible in Access. Some things can't be done with an SQL query. Even a VFP query. It takes tuned code.