While researching what is involved to upsize/migrate our application to use a SQL Server back end, I recalled that that my colleague wanted to achieve having a single set of code that supported the use of either SQL or VFP as the data engine (depending on the client site). I think the reasoning for this is because we cannot anticipate all of our clients wanting to migrate to the SQL version at the same time.

I was curious if anyone here has had experiences (be they good or bad) in the scenario described above. Are we looking for headaches?

Any insight would be greatly appreciated.

Laterness,
Jon