Linked tables using odc (reference problem, runtime)

[John =?ISO-8859-1?Q?=D8llg=E5rd?= Jensen]

Hi,

My Access 2003 client application is partly using linked tables located
on a Ms SQL Server. Datasource is accessed using odc (Office data
connection).
When the odc was created on the development machine, an odc file was
created and placed on the developers machine (locally).

Now I want to make a runtime installation package to be destribuated to
several runtime users.
How can the odc-file be referenced by my client application after
installing on other PC's? And should the odc-file be included in the
installation package?


regards John

 

[MGFoster]

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


Use a DSN-less connection string in the tables/queries. Example of DSN
less connection string:

ODBC;Driver={SQL
Server};Server=MyServer;Database=DBName;Trusted_Connection=Yes

Substitute your server & database names. The server name can be an IP
address. Trusted_Connection=Yes means the SQL server is using NT Logon
authentication instead of SQL Server authentication. If you're using
SQL Server authentication then substitute

UID=UserName;PID=UserPassword

for the Trusted_Connection parameter. Put in your own user IDs &
passwords.

You'll have to change the TableDef.Connection property programmatically
(VBA). You can change the QueryDef's ODBC connection string manually or
programmatically.

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

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

iQA/AwUBQT9epIechKqOuFEgEQKfuACgmB3jF55iMYDnJ0CMEzdqZeJTipYAoLTc
iDFZMCjDK4NF1gufroFrBqsq
=7KRC
-----END PGP SIGNATURE-----