DAO Recordset and Data Control

You don't have to use a DC.

Declare a class or form level variable as DAO.Recordset, this will let it stay open as long as the form or class is alive.

Open your recordset the normal way, then assign it to the RecordSource (DataSource?) property of your grid using code:

Set DBGrid1.RecordSource = m_rsGridData

(forgive me, I don't work with bound controls that much, and I can't remember the exact property name).

Just remember to close and set to Nothing your Recordset objects in the terminate event of your class or form.

Glen

For Answer #1:
I am afraid that this is not working for me. I know how to handle classes, recordsets, and use my own data enviroment classes.

The problem is that setting the datasource of a DBGrid control, (Not an ADO datagrid control), to a DAO recordset doesn't seem to be supported by the DBGrid control at run time as is the ADO GridControl. I am only able to set the recordsource to a DataControl in the IDE. Therefore I said that I believe the only way is to use the datacontrol and therefore, my question is, if this is so, how can I still manipulate everything via my recordset, (without setting properties or using the methods of the datacontrol except for maybe setting the datasource).

I will raise the points and also leave youranswer unrated for a few days incase you have more ideas, not wanting to reject it right away....

Point value changed by question poster.

I base all of me forms on a query AND use a list box on each form to replace the data control for record navigation. My forms are all DAO (only) and the data control is not even displayed. On the Toolbox click Combo Box and place it on your form -then select "Find a record on my form based on the value I select"., then select a UNIQUE field common to the form and combo box.

For Answer #2:

Sorry, I hit the button too fast. I wanted to also leave your answer open in case you came up with something else......Anyways, your response is appreciated!

Point value changed by question poster.

Point value changed by question poster.

Ok. I am going to close this in a few days. If someone is working on an answer then e-mail me and I will wait before closing......Looks like I am stuck with using the DataControl in VB6 and DAO for the DBGrid /:(

Ok. I've let you smore long enough, (remember?)

Unfortunately, you MUST use the datacontrol. But you CAN set a recordset object to the datacontrol in DAO with-out having to set any other properties. Not too many people know how to do this, and a while back it took me a sometime to figure it out, but it is very simple. First, you do not set the RecordSource, (as I tried to). You SET the datacontrol's recordset OBJECT to YOUR recordset object! You do not have to do anything else - not even setthe database or connection properties - it will take on the identical properties as your rs object.
Then all repositioning, methods, etc, that you use on your recorset object will affect the datacontrol's rs and in turn the DBGrid, even additions and deletions. The only thing that you need to do extra is re-set it again if you re-open the recordset, (like after changing the SELECT statement when changing criteria or sort order - if you cannot use the sort/filter methods of the recordset because it is not a Jet Db).

It's the best that can be done with-out using the grid in unbound mode( alot of work).

Ok? Ok!

This question was closed by the author