The first thing to realize is that ALL data access is via SQL statements. You can't SEEK, LOCATE, DELETE, REPLACE, etc. You need to work with a set of data, for example all customers with a LastName = "Smith". So using a SQL SELLECT statment, you get that set of data and work with it. You NEVER have the entire table. ALWAYS a set of data.

Next, connecting over a VPN is no different than connecting locally. You have a connection string that includes several things, including the servername. You may or may not have username and password. It depends on how SQL Server was configured. If it uses WIndows Authentication, then Windows will pass an authentication token to SQL Server and no username/password is required from the user. If you use "Mixed" authentication, you may have to pass a username and password as part of the connetion sstrnig OR you can rely on Windows Autentication. It depends on how that user was setup in SQL Server.

You also need to determine what technology to use inside VFP. See my other post ot you.

>Hi Craig,
>
>I don't have experience with SQL Server. I have some experience with Interbase ( Borland SQL ) but it was on a local machine and I used at this time an ODBC driver to build my connection.