>>>>Yes, I was using the handle returned from VFP function SQLSTRINGCONNECT. My bad. I will try to use the GetConnect() from the sample; the only thing I don't know is what you use for the DSN name parameter. The syntax of calling GetConnect() is GetConnect("dsn", user, password). What do you use for DSN? Thank you again for your help.
>>>
>>>Can you make a DSN for now in order to test?
>>
>>How do you make it?
>
>1. Create an ODBC data source :
>a. Go to Control Panel > Administrative Tools and open Data Sources ODBC. -- if you're using Windows 64 bit, then
>type odbcad32.exe in the Search box
>
>b. Click on the System DSN tab and click the Add button.
>c. Select SQL Server from the list (usually the last entry)
>d. Click Finish.
>2. Enter some name into the name box and pull down the Server list and select (local) or the server name
>where SQL and the data are installed. Click Next.
>
>3. Select the SQL Server authentication radio button.
>a. If this is not the server.
>1. Click on the Client Configuration button.
>2. If necessary, change the Network Library radio button selection from Named Pipes to TCP/IP and
>click OK.
>4. Enter a username and password of uID and password and click Next. For testing purchases you can
>also use another known account in SQL Server, such as SA.
>5. Uncheck Use ANSI quoted identifiers and click Next and then Finish.
>6. Click on Test Data Source and confirm the test completed successfully.


FYI:

You can export the registry ODBC System DSN items from a windows 7 32 bit (or xp etc) and then rename it something like odbcwindows7_32.reg and then in the .reg file, edit the path

from:

SOFTWARE\ODBC\

to:

SOFTWARE\Wow6432Node\ODBC\

and they will work. They will show up using odbcad32.exe as well and in the correct location in the registry.