A particular team in my office uses 100's of Microsoft Access Models. They all connect with the database using SystemDSN and, the name of the SystemDSN is hardcoded in the Microsoft Access Models.
My teammate suggested that we use a login script to ensure that the SystemDSN is configured for all users who belong to that team. For example, if a new joinee comes along, he gets the DSN automatically rather than calling IT for manual setup.
I am suggesting that we use FileDSN, store the FileDSN on a network share path and be done with. The advantages being the following
If I were to migrate by database to a new server, I need to just update the FileDSN at one location and all done.
I can access the Microsoft Access Model even via Citrix where I may not be able to have SystemDSN as such.
The problem, as my team mate suggests, is
- There are over 100 Microsoft AccessModels, so, how do you go about changing the hardcoded values of SystemDSN? He claims that it is not worth the effort.
Surely, there should be a programming concept for us to make the change at one go.
While I continue to rack my brain for a solution, if someone out there already has one do let us all know!