adamgoossens
New member
- Local time
- Today, 17:19
- Joined
- May 25, 2005
- Messages
- 8
Hi all,
The client for an Access Data Project I am working on would like the ability to be able to install the back-end MSDE database onto an arbitrary computer and then connect the front-end application up to it (presumably after being prompted for connection details).
Currently, my installer bootstraps MSDE to the local machine and then installs the ADP - since the ADP's data source is set to "(local)", everything hooks up nicely.
Normally, to change the data source I'd have to go to "File->Connection...", etc, but this opens up the database in a way I don't really approve of. The less interaction the user has with the "guts" of the ADP, the better (and besides, I would prefer to distribute a bypass-key-disabled ADE if I could).
Does anybody know of a way to do this dynamically via code, without having to use the bypass key to set it manually?
Many thanks,
-Adam.
The client for an Access Data Project I am working on would like the ability to be able to install the back-end MSDE database onto an arbitrary computer and then connect the front-end application up to it (presumably after being prompted for connection details).
Currently, my installer bootstraps MSDE to the local machine and then installs the ADP - since the ADP's data source is set to "(local)", everything hooks up nicely.
Normally, to change the data source I'd have to go to "File->Connection...", etc, but this opens up the database in a way I don't really approve of. The less interaction the user has with the "guts" of the ADP, the better (and besides, I would prefer to distribute a bypass-key-disabled ADE if I could).
Does anybody know of a way to do this dynamically via code, without having to use the bypass key to set it manually?
Many thanks,
-Adam.
Last edited:
