Thanks, I'm getting much closer now but I'm still missing a few pieces of the puzzle.
To summarize so far, to ship an EXE that uses remote views of SQL Server tables:

In development environment, create a DBC. In the DBC, create a named connection using a DSN, then create remote views based on this connection. Code the app using these remote views.

When the EXE is shipped to the field, before running the EXE, the end user must first set up a DSN either through the ODBC wizard or by running a VFP routine containing the code provided by Mr. Flores.

When I tried the DSN approach in my development environment, I was unable to connect. Possibly two reasons: 1) I don't see how the DSN knows the name of the SQL server. 2) The connection was created using the driver "SQL Server (32 bit)" instead of plain "SQL Server". Does this matter?

Assuming the DSN is working, for the next step, the app should prompt the user for the DSN, user id and password. A list of available DSNs can be generated from the code provided by Mr. Lucas. Here's where I'm confused again. Once you get this information from the user, how do you update the connection with it? I can browse the DBC and see the Property field in the Connection = 'ObjectType' record should get updated, but how? By directly writing the record or is there some other VFP command to do this?
Thanks,
-John