preparing a DB for users to install.

[webcat]

Hi

i have pretty much finished a complex DB app that uses 2 DSNs for 4 linked tables.

The DSNs work, but when i ZIP up the DB file and ask others to create the DSNs exactly as I have them on my machine, the linked tables fail on the other persons system

I am using SQL server authentication

what I have to do to get the tables working is hold shift at startup to show the tables and then update them. This works for one DSN, but the other three tables have to be deleted and re imported.

i need an easy to deploy way of fixing this. my users should not have to do this to install the DB.


has anyone got any tips on how to pre-setup linked tables so they will work on anyone's system - after the DSNs have been setup correctly.

thanks for any ideas

 

[KeithG]

I wouldn't use a DSN. check out the below site which has a number of connection string to various RDBMS.

www.connectionstrings.com

 

[boblarson]

Also, make sure the users have the appropriate permissions on the SQL Server.

 

[webcat]

interesting,

but how do i implement that ?

 

[webcat]

thats interesting...

but, how do i use that command ?

Driver={SQL Server};Server=serverName;Database=Tracker;Uid=Tracker;Pwd=xxxxx;

 

[KeithG]

I would use a pass-through query instead of a linked table