automate ODBC rollout

[sard0nicpan]

Hi, I'm trying to get my head around a problem. I have about 20 clients to provide for an Access front-end(Sql Server back). I have already written a File that fetches the mde, creates directories on the client, and then copies the mde to the proper destination. This works out great, but of course, I still have to provide the ODBC connections to the DB/dsn for each station.

I followed thread 779-683406, however I'm not sure, I understood what I was to do. For the sake of a concrete example, lets say my DB dsn name is AFETrans.dsn. How do I script that in a bat file to make the proper registry settings without having to run to 3 floors and 20 stations in person? The desktops in question have either Pro XP or 2000.

One member in the thread commented that the line needed to be included in the bat file:
start regedit/s C:\myPC\AFETrans.reg

Is that all? What does "/s" do? I guess before I do something I'd like to understand what I'm doing rather than just proceed like a robot. Can anybody educate me a bit, or at least point me to a good reference?

There was also a question of whether the technique would work with XP. Most of the computers are 2000, so having to do a few XP's in person would not be too onerous.

Any help and pointers appreciated.
Thanks in advance,
Tony

 

[ArtieChoke]

Your best bet is to use a file dsn. It doesn't require registry entries and can be located on a server. Then if the database location changes, you only have to change the DSN in one place.

Also, why not put the mdb file on the server and put shortcuts to it on the clients? That way if you need to modify it, you only do it in one place. If you're allowing the users to modify their copy, then that won't work in this model.

If you still want to do the registry thing, search this forum. I answered another thread about which entries you need to extract from the registry and store on the client machines.

To answer your question about the "/s" switch for regsvr32, it's silent mode - it won't display a message box after registering the dll file (which would wait until you press okay - not good for batch files - doh!).

"I think we're all Bozos on this bus!" - Firesign Theatre

 

[sard0nicpan]

Thanks AC,

Unfortunately, my immediate superior does not want to link shortcuts to the server (I'm not really sure, this was my first suggestion). However, perhaps your post may convince him otherwise.

Thanks for your attention,
Tony