Printable View
I posted this problem recently and I got the answer that I should substitute ADO controls. However the project is completed and at this point, substituting ADO for DAO is turning out to be pretty sticky. I can't believe that this problem has not been resolved in all the years that DAO has been operational.
If anybody knows how I can get these data controls to release memory properly I sure would appreciate hearing from you. I am using VB6 SP6 on XP.
Thanks. Indio
DAO was first introduced back early 90s and was primarily based on JET Engine wich is limited to begin with.
How do you expect DAO to be reasonably operational outside of MS Access I really don't know - I think even MS Access now uses ADO as primamry data access library.
And I am only referring to DAO library - not DAO data control which is even worst.
I don't want to turn this totpic into another data binding vs non biding - not at all.
The point still remains - substitute DAO for ADO as it is much more robust and flexible data interrface.
Also, you'd be doing yourself a big favor but not using any data control at all.
It doesn't matter if it takes time to completely re-write your app - it wasn't done right in the first place and that is some thing that you have to realize finally.
Good luck and sorry for not being very helpfull.
Thanks for your resopnse; I am using Access exclusively and I'm using the data control to populate some grids and combo boxs. If I could do this stuff without using a data control it would be great (I'll look into that).
As you suggested, I'm in the process of substituting ADO for DAO.
Thanks again,
Indio
In that case, look at the "Classic VB" sections of our Database Development FAQs/Tutorials (at the top of the Database Development forum), which covers most of what you need (particularly Beacon's tutorial).
There is also a link in my signature to fill a FlexGrid from a recordset.
Thanks, I really appreciate it. Indio
The tutorial was really helpful (understatement).