I use code to modify the connection properties of an ADP project. Once set, these properties tend to "stick" to the ADP file, and a subsequent re-open of the project and look at the connection properties confirms this.
This situation is fine, providing the connection exists, and can be made.
I now wish to / need to be able to move an ADP from one environment to another (for Disaster recovery purposes), and need to be able to pass the connection string via command line parameters. No problem here. I find however that when the project initiates, the "hard coded" connection string will cause failure. I am unsure how to trap and deal with this, as it seems to occur before the Autoexec macro fires, from where I would deal with the connection dynamics.
Anyone got any epxerience with this. How do I trap and deal with the invalid connection properties when the ADP is opening.
TIA,
Steve
Steve Lewy
Solutions Developer
SimplyData
simplydata.com.au
(dont cut corners or you'll go round in circles)
This situation is fine, providing the connection exists, and can be made.
I now wish to / need to be able to move an ADP from one environment to another (for Disaster recovery purposes), and need to be able to pass the connection string via command line parameters. No problem here. I find however that when the project initiates, the "hard coded" connection string will cause failure. I am unsure how to trap and deal with this, as it seems to occur before the Autoexec macro fires, from where I would deal with the connection dynamics.
Anyone got any epxerience with this. How do I trap and deal with the invalid connection properties when the ADP is opening.
TIA,
Steve
Steve Lewy
Solutions Developer
SimplyData
simplydata.com.au
(dont cut corners or you'll go round in circles)