I think it's great that you have a tool to do some of this, but the application I have is already in production - this is not something we are building. The client is needing to move to a SQL backend because of the size of the data tables reaching the 2gb limit. We have already partitioned the problem tables once, and do not want to do it again.

I was looking for real world experience with linked servers... I am not interested in trying to incorporate a 3rd party tool for something that will eventually not be necessary at all - when the client's tables are all on the SQL Server.

We use views for all the forms, and will be able to keep that as the case even when the tables are moved to the SS, but any code that is currently written to join the tables in VFP (currently straight selects) is going to have to be rewritten to 1) process locally and then look for the corresponding child records on the server, or 2) the code will have to be sent to the SS, processed (by linking the db and using the joins there) and sent back to the client application.

We are just looking for comments on stability, speed, etc. We may not linked servers as a solution.