Very Computer

[ADODC]:  no RecordSource specified. [ADO]: Command Text was not set for the
command object.

I do NOT want to set the recordsource property at design time.  What can I
do to avoid the error when the form loads?  This error happens when I load
the form in the IDE in design mode as well.  The recordsource was never
required at design time with DAO data controls.  What am I missing?  Thanks,

Bill

Everything I've read makes it sound very simple and says to set the
connection string at design time, and then change the connection string with
the Form_Load event. I have tried this and it doesn't work. When the form
loads, it still tries to connect to the hard-coded connection string. If the
file is not in that location, I get errors, and the commands in the
Form_Load event never occur. How do I set the connection string at run-time
so that I can use the app.path.

Below is the code I am trying in the Form_Load event (I have also tried it
in Form_Initialize):

Adodc1.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" &
App.Path & "\Funds.mdb;Persist Security Info=False"

-Brent

Quote:> Hello all,
> I'm trying to set an ADO data control's recordsource at runtime, but when
> the form loads, I get the error for each data control on the form:

> [ADODC]:  no RecordSource specified. [ADO]: Command Text was not set for
the
> command object.

> I do NOT want to set the recordsource property at design time.  What can I
> do to avoid the error when the form loads?  This error happens when I load
> the form in the IDE in design mode as well.  The recordsource was never
> required at design time with DAO data controls.  What am I missing?
Thanks,

> Bill

Hope this helps!

Ramesh Thyagarajan, MCSD,MCDBA
Microsoft Developer support

This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Microsoft Strategic Technology
Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

Thank you very much!!

-Brent

Quote:> Hello Bill and Brent,
> You are seeing this error messsage because you set part of the ADO
> Datacontrol's properties at design time and some of it at runtime.
> This error was caused by the setting the ADODC Connectionstring property
in
> design time, but not its Recordsource property.    My suggestion will be
to
> set all the pertinent data control properties in runtime, i.e. the
> Connectionstring, Recordsource, and Commandtype.  Once assigning
> appropriate
> values to these properties in code, the next step will be to execute the
> ADODC Refresh method.

> Hope this helps!

> Ramesh Thyagarajan, MCSD,MCDBA
> Microsoft Developer support

> This posting is provided "AS IS" with no warranties, and confers no
rights.

> Are you secure? For information about the Microsoft Strategic Technology
> Protection Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.

Do you or anyone know an issue of doing without adodc? I'm using datagrid
connected to db without adodc. I'm curious and worrying whether there is a
problem in my behavior.

rst.CursorLocation = 3
rst.Open "SQL",CON,1,3,1
Set datagrid1.DataSource = rst

--
Han Pohwan, Seoul/Korea

Quote:> Hello Bill and Brent,
> You are seeing this error messsage because you set part of the ADO
> Datacontrol's properties at design time and some of it at runtime.
> This error was caused by the setting the ADODC Connectionstring property
in
> design time, but not its Recordsource property.    My suggestion will be
to
> set all the pertinent data control properties in runtime, i.e. the
> Connectionstring, Recordsource, and Commandtype.  Once assigning
> appropriate
> values to these properties in code, the next step will be to execute the
> ADODC Refresh method.

> Hope this helps!

> Ramesh Thyagarajan, MCSD,MCDBA
> Microsoft Developer support

> This posting is provided "AS IS" with no warranties, and confers no
rights.

> Are you secure? For information about the Microsoft Strategic Technology
> Protection Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.

Matt

Quote:> Hello Bill and Brent,
> You are seeing this error messsage because you set part of the ADO
> Datacontrol's properties at design time and some of it at runtime.
> This error was caused by the setting the ADODC Connectionstring property
in
> design time, but not its Recordsource property.    My suggestion will be
to
> set all the pertinent data control properties in runtime, i.e. the
> Connectionstring, Recordsource, and Commandtype.  Once assigning
> appropriate
> values to these properties in code, the next step will be to execute the
> ADODC Refresh method.

> Hope this helps!

> Ramesh Thyagarajan, MCSD,MCDBA
> Microsoft Developer support

> This posting is provided "AS IS" with no warranties, and confers no
rights.

> Are you secure? For information about the Microsoft Strategic Technology
> Protection Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.

Hope this helps.!

Ramesh Thyagarajan, MCSD,MCDBA
Microsoft Developer support

This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Microsoft Strategic Technology
Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

--
Han Pohwan, Seoul/Korea

Quote:> Hello Han,
> I have not encountered anything specific with not using ADODC.
> ADODC is easy for simple applications. But doing everything thru code, you
> have more control over the code.
> I prefer doing it through code so that I dont have to rely on settings I
> make at design time.

> Hope this helps.!

> Ramesh Thyagarajan, MCSD,MCDBA
> Microsoft Developer support

> This posting is provided "AS IS" with no warranties, and confers no
rights.

> Are you secure? For information about the Microsoft Strategic Technology
> Protection Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.