>>>>We distribute the VFP app. Every customer starts with a brand new database created on their server by the VFP app. The app handles updates to schemas and stored procs also. In other words, when there are schema changes, the customer only needs to receive the updated VFP tables, and the app will apply only the latest schema changes. This is how we "version" our database.

I'm considering this right now, it seems to be a very good approach - thank you. I'm also considering minimizing our app's SQL interaction to just look up, updates and deletes - no stored procs - so we don't get locked into one vendor's SQL (we see choice of SQL vendor (obviously either Oracle or Microsoft) is like a religious war with consultants). Question: could you do your entire app without stored procs?

>>>>Currently, we're pushing SQL Server, not Oracle. If a customer wants Oracle, we try and talk them out of it. <g> Seriously though, we haven't run into that obstacle yet.

Where did your app get married to Microsoft SQL? In their Transact-SQL language? I can see this happening, I don't want any part of it. If I could only just be a programmer I'd be very happy.