Installing ODBC Connections at Each Workstation

[dzdncnfsd]

I have created an Access 97 database frontend that connects to a MSSQL 7.0 database backend. They reside on different NT 4.0 servers that everyone in the company has rights to under NT. I am trying to avoid having to go to each workstation to (1)upgrade drivers and then (2)create the ODBC connection. Is there a way to create a "global" connection?
Thanks for any help you can give.
Gladys

Gladys Clemmer
gladys.clemmer@fifsg.com

 

[foxdev]

I'm not an Access user, but I have two ideas:

1) Use a "File" DSN rather than a "User" DSN; the File DSN can be shared by multiple users and placed on a network. We've used this technique successfully in connecting an Excel spreadsheet to SQL Server.

2) If Access supports it, use a DSN-less connection string. The connection string won't require a DSN, and includes every parameter needed to connect (server name/address, database, username, password, etc). Robert Bradley

http://www.foxdev.com/

Got extra money lying around? Visit:

http://www.agrainofhope.org

 

[dzdncnfsd]

Thanks, Robert, I am experimenting with option 1 now, but since I have newer driver versions than most everyone else, will they be able to use what I create? And do I place them in a folder on the network and make that the default "look in" folder for each workstation?
For option 2, would the connection string go in a module of the Access DB? I know you use SQL and VFP, so I am assuming it would work the same with Access and SQL.
Thanks.

Gladys Clemmer
gladys.clemmer@fifsg.com

 

[Guest_imported]

Depends on your clients and how locked down they are - Microsofts MDAC installer (MDACTYP.EXE) can be used to update clients and has a "quiet" install option (-q I think) so could be run from a login script (might need a flag file to use If Exist on to check if done already unless you are using something clever like KIX for login scripting (whcih I recommend as it is good AND free))

If clients are NT / 2K etc then they might be locked down so that only admin can install etc.

As for DSN's - file DSN's are good - but also you can use a REG file (export the registry tree from Regedit - keys are under HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI for Machine DSN's , as this but HKEY_CURRENT_USER for user DSN's) then you can use Regedit from a script to merge them in (-s makes this silent too) this again assumes registry access ok for the user