> It works ... it actually works!!! Now what? Go home, you've had a tough day! (S) > Can I just update existing records and add new ecords? Then use > TableUpdate() to update the table in the dbc. You only need the table update if you are using remote views, not if you are using PassThrough to insert/modify. The best use of passthrough, IMHO, is to pass parameters to stroed procedures on the Server to do the updates. It isn't as "clean" (again, IMHO) to do updates by using Insert/Update via pass-through. Check out using remote views as well. that is really cool as you can bind your data to forms much easier..... > I am developing on dbc\tables on my pc and want to ventually have the files > on MS SQL Server. That is the best way to practice C/S as you won't tick off your DBA (my day jog (g)) by playing trial and error with a production server. It all pretty much works the same. One thing to consider, is to use local view prototypes and then upsize the whole thing to SQL server. Not only will it move your data structures and data to the server, you local views become remote views instantly. You just have to make sure you applied buffering and etc...... > Do I just have to redefine my OBDC connections to MS SQL Server? Is that > all there is to ODBC and lient-Service? Am I missing something? That's pretty much it. VFP just works through ODBC and it desn't care whats on the other side. There are MANY benifits of SQL Server such as security, stored procedures, etc, etc. Easy, huh? HTH, Scot.