MDAC architecture may be viewed as three layers: a programming interface layer, consisting of ADO and ADO.NET, a database access layer developed by database vendors such as Oracle and Microsoft (OLE DB, .Code runs absolutely perfectly in design mode - just refuses to compile. Fails with the data control Connect property set to Access and also Access 2000. if its not too much of an effort to create a fresh project and set all required references and then include the forms and other files into it. "First Record and Last Record native buttons on the data control do work however." that makes me suspect you do have a reference to both DAO and ADO if so, and you do not use any ADO methods, remove the reference to ADO if you do use ADO methods you can do 1) move the DAO reference ahead of the ADO reference or 2)prepend all your DAO objects with DAO (ie: DAO.database, DAO. This is a legacy project on an Access 97 database, so it's DAO 3.5 I presume. I wonder if a Jet dependancy dll is missing or incompatible version? I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing.You'll be able to ask any tech support questions, or chat with the community and help others.(Data 1 is a plain vanilla data control on form F.) Only change to PC was installation of some junk VB6 application which wrecked the registry. Removed that, went back to prior system restore point and restored the source code from backup. I'm guessing a DLL is not registered or is corrupt - but which one? Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S. Even a trivial program in design mode throws an "Error in Loading DLL " error when it tries to execute Data1. Move Last (or indeed any command on the recordset.) Probably did not see that in design mode before as I never executed such a statement. In the simple test application which fails, the only references are: Visual Basic For Applications Visual Basic runtime objects and procedures Visual Basic objects and procedures Microsoft DAO 3.51 Object Library That's correct I think. "The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years.First Record and Last Record native buttons on the data control do work however. Recordset,etc...) or 3)prepend your DAO objects with DAO and your ADO objects with ADODB also if your database is access2000 or your datacontrols connect property should be Access 2000 and you should have a reference to DAO 3.6 prior to Access2000 it should be Access and you should have a reference to DAO 3.5 It is VB6 that is broken rather than the application. Hi, Do you still have problems if you try a small project without DAO involved?
At that time Microsoft stated MDAC was more a concept than a stand-alone program and had no widespread distribution method.
We're a friendly computing community, bustling with knowledgeable members to help solve your tech questions.
Please join our friendly community by clicking the button below - it only takes a few seconds and is totally free.
There have been several deprecated components as well, such as the Microsoft Jet Database Engine, MSDASQL (the OLE DB provider for ODBC), and Remote Data Services (RDS).
Some components have also become obsolete, such as the former Data Access Objects API and Remote Data Objects.