adodc startup confusion

[northrd]

All thing being equal how does one trap a connection error with an ADODC during application startup thus stopping the same error occuring with other ADODCs?

Or, put another way, am I doing the wrong thing by "hard-coding" the connection details of the ADODC into the IDE?

 

[JoeAtWork]

In my opinion, using data controls at all is generally the wrong choice.

However, if you do use them, then yes, your hunch is right, don't set the connection until runtime. You can test if the connection is valid by first trying to open an ADO Connection object with the same connection string (and trap the error).

 

[northrd]

Cheers

yep, tried the "easy" way with ADODCs.

Cheers