I have a pretty large app that I need to change to let it use a Fox or SQL Server back end. There are a LOT of data entry screens bound to fields, so I'd like to handle them with remote, updateable, parameterized views. Reports, etc... will most likely use SQL pass through. Using ADO to abstract data access is probably more than I can do in the amount of time I have, besides, it would slow down the really fast native access.

I've found that the upsizing wizard did a fair job of creating remote views. Stonefield Database Toolkit keeps the views in synch with the back end pretty easily as structure changes are made.

So far it looks like it will work without a huge amount of effort, but questions are popping up.

1) The connection name seems to be inextricably bound to the view. Can't even hack the .DBC for this one. That means I can't switch to an alternate database unless I point my ODBC DSN to another machine with a database of the same name. Any elegant ways around this? A set of training data on the same server would be very helpful.

2) Is there a utility to keep the database structure in SQL Server in synch with the Fox database? Since we will be supporting both, I'd like to avoid making manual changes to both.

Thanks in advance,
Mike