My suggestion is to NOT use a DSN. It is too easy for your application to break. Rather, I would rely on a string-based connection. Here is a sample DSN-Less connection string:

DBQ=C:\Program Files\Microsoft Visual Studio\VB98\NWIND.MDB;DefaultDir=C:\Program Files\Microsoft Visual Studio\VB98;Driver={Microsoft Access Driver (*.mdb)};DriverId=281;FIL=MS Access;MaxBufferSize=2048;PageTimeout=5;

Like any string, you can dynamically build it and establish a connection to the database. If you always know the location of the MDB file, your job is that much easier...

You can create a connection object in the dbc like this:

Create Connect accessconnection ;
   connstring "DBQ=C:\Program Files\Microsoft Visual Studio\VB98\NWIND.MDB;DefaultDir=C:\Program Files\Microsoft Visual Studio\VB98;Driver={Microsoft Access Driver (*.mdb)};DriverId=281;FIL=MS Access;MaxBufferSize=2048;PageTimeout=5;"

Your remote view then will reference the connection, not a DSN in order to establish a link to the MDB.

There are lots of strategies out there to handle this issue and I am sure other folks will chime in..

HTH...



>What do I need to do to set up a DSN entry on the customer's machine? I am relying on the DSN ertry to connect to the Access database.
>
>Lance