losing DSN when moving query from test to production

[Rebecca Culver]

Hello --

I'm using some Access queries linked to an SQL database. My test and
production environments have the same table names, just different DSNs
in my system.

When I export my query to my production database, which is linked to
the production DSN, my queries stop running. Does anyone know where
the link information is hiding so I can repoint it?????

thank you

 

[MGFoster]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

If you're running an .mdb Access db, the info is in the query's
Connection string property.

It might be better to use a DSN-less connection string instead of a
DSN, then your users would not have to have matching DSNs set up on
their PCs.

A DSN-less connection string example (LAN connection) (all one line):

ODBC;DRIVER=SQL Server;SERVER=ServerNameOrIPAddress;UID=UserName;
DATABASE=DBName;Trusted_Connection=Yes

Trusted_Connection means the user can sign on to SQL'r using their NT
logon name & permissions.

- --
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQBblrIechKqOuFEgEQL2UwCfSa4LWtgl2aXygoLoacZmycaUkb8AoK1w
qvUfFJoxrddoHmWZwDm7+5li
=ngPK
-----END PGP SIGNATURE-----