ChipperT
Banned in 13 Countries
- Local time
- Today, 12:00
- Joined
- Jun 1, 2010
- Messages
- 347
I am tasked right now with maintaining several VB.Net apps that use an Access backend with ADO. I don't know who wrote them and, in any event the authors are long gone. Each of the apps use UDL files to pass in the connection string. None are password-protected. I can't figure out why the UDL files are used and no one can tell me what the logic would be. My boss wants me to leave it that way but I am tending to change the connection string to the app code.
Can anyone tell me a good reason to use UDL files (other than the ability to easily switch the DB connection to point from test to prod dbs)?
Can anyone tell me a good reason to use UDL files (other than the ability to easily switch the DB connection to point from test to prod dbs)?
Last edited: