ADO Connect String

[Danny Desmet]

When developping a program using a ADO Data Control you have to build a connect
string (p.e. a connection to an access database) wich remains hard coded.
When porting the program to an other computer where te database is located
in an other directory , the program do not work any more.

I have tried the following :

Before using the ADO data control I change the connect String with a new
value :

p.e. form.datacontrol.ConnectString = "............."

Even then the datacontrol still tries to connect to the hard coded connect
string

How do i have to solve this problem ???


Thanks,

Danny Desmet

[Dan Appleman]

I haven't used the ADO data control - I tend to use ADO directly. I haven't had a
problem changing the database
connection string there.

Dan


Danny Desmet wrote:

> When developping a program using a ADO Data Control you have to build a connect
> string (p.e. a connection to an access database) wich remains hard coded.
> When porting the program to an other computer where te database is located
> in an other directory , the program do not work any more.
>
> I have tried the following :
>
> Before using the ADO data control I change the connect String with a new
> value :
>
> p.e. form.datacontrol.ConnectString = "............."
>
> Even then the datacontrol still tries to connect to the hard coded connect
> string
>
> How do i have to solve this problem ???
>
> Thanks,
>
> Danny Desmet
>
>

[Danny Desmet]

When using ADO directly there is indead no problem but in some cases (p.e.
when you use a control that is bound to the ADO datacontrol - p.e. a True
DBGRid) there is no choice.

Danny Desmet



Dan Appleman <dan@desaware.com> wrote:
>I haven't used the ADO data control - I tend to use ADO directly. I haven't
had a
>problem changing the database
>connection string there.
>
>Dan
>
>
>Danny Desmet wrote:
>
>> When developping a program using a ADO Data Control you have to build
a connect
>> string (p.e. a connection to an access database) wich remains hard coded.
>> When porting the program to an other computer where te database is located
>> in an other directory , the program do not work any more.
>>
>> I have tried the following :
>>
>> Before using the ADO data control I change the connect String with a new
>> value :
>>
>> p.e. form.datacontrol.ConnectString = "............."
>>
>> Even then the datacontrol still tries to connect to the hard coded connect
>> string
>>
>> How do i have to solve this problem ???
>>
>> Thanks,
>>
>> Danny Desmet
>>
>>
>

[Phil Weber]

> When developing a program using an ADO Data Control,
> you have to build a connect string which remains hard-
> coded. When porting the program to an other computer
> where the database is located in another directory, the
> program does not work anymore.

Danny: I would suggest clearing the data control's Connect property at
design time and setting it in your initialization code (Form_Load or Sub
Main) by reading the database location, etc. from the registry or an .INI
file.
---
Phil Weber