Hi,

This is intended for those who are considering/worrying about going SQL Server from VFP. Those experienced in this will probably find most of this old news.

I recently returned from installing the first SQL version of our Vert. App for 3 companies at 2 sites. It was previously a pure VFP 5.0 App and is now VFP6/SQL7. Overall - everything went very well. The few problems I've had have been "new app" related as opposed to anything SQL or Client/Server specific. Some tidbits:

- Install and setup went very well - no unanticipated issues

- It is orders of magnitude faster over the internet than VFP. It is VERY USABLE - sometimes barely slower than LAN going over the Net. I'm still confused as to why anyone would jump through HTML/Web Server or Citrix hoops for in-company application when the program going straight to the server works very well - even with a 56K modem on the client side!!

- somewhat to my surprise - it is actually quite a bit faster over the LAN than its predecessor!!!!

- I LOVE SQL Server - I also love VFP and being able to make data do backflips when I have it locally. I'm using a few cliient side tables for various things and the combo of VFP/SQL is great for my application.

- favorite SQL Server Features:
------------------------------------------------
- SQL Agent and automated integrity checks and back-up
- STORED PROCEDURES!!!!!!!!! Wow - my "tweaking time" for many things has been cut into a fraction of the time! Now I just pop in to their server over the net, change a stored proc, and voila! everybody's got it. No recompiling and redistributing the VFP app for many of my fixes. Client is AMAZED when they call me with an issue and while on the phone I say - "wait a minute - ok - try it now" and it is fixed!
- SQL Profiler has proved invaluable in development and in finding/fixing a few post-installation issues

Some basic technical info on what I did:
------------------------------------------
- I used stored procedures as much as possible - VERY GLAD I DID THIS - most I ever pass in from client is a procedure call and a WHERE clause
- I used SPT exclusively - no remote views - and thus no VFP database - ALSO VERY GLAD I DID THIS
- I use SQLStringConnect - I have no DSN to worry about - another groovy thing
- Have all business rules stored as data in tables and implemented through a virtual middle tier
- Put all RI as SQL Triggers - and, as said above - Bus rules in middle tier - I do have some front-end validations where they make sense
- look-up tables stored as local VFP Free tables - repulled when B/E changes
- All integer/surrogate keys = all primary keys are Identity columns in SQL
- All data conversion was handled through VFP as opposed to DTS - went very well and I had more control.

What I would like to have done (and will do) different
-----------------------------------------------------------------------
- Even more stuff as stored procedures -
- More things driven by meta-data
- will probably rework my security from scratch

In Conclusion - I feel very good about the whole thing. It is working well and the fact that I can now administrate over the net in a practical manner is invaluable. For anyone hesitating about making the move - DON'T - Best decision I ever made. I am now looking forward to implementing ASP and other langages (VB?) for various tasks, modules, or related applications. I will probably begin a gradual move away from VFP to be honest - but am in no hurry as it is working well for me now and I have a ton invested in my framework and application.

I'd be happy to answer any specific questions if it would be of value to anyone.

Thanks,
Ken