Cant find member error

[mathisjay]

I made an Access application for a potential client. I have v.2003. The application works great on my machine. However, after I made it, I found out the client only has v97. So I tried saving the DB down to v97, but there were alot of tings that didnt convert down very well. So, the client "upgraded" to v2000 (I don't know why they didnt just upgrade to v2003), I converted the app down to v2000 and tested it out and it seems to work fine on my machine.

I sent it over a beta version to the client to play around with, but they are saying they get a bunch of errors when they try to open it. From the sounds of it, it sounds to me like an MDAC issue. It seems to bomb out any time the code tries to create an ADO recordset object. I know v97 used DAO but I figured when they upgraded to v2000, that it wold have all the libraries for ADO, but apparantly not.

So, how can I fix this problem? v2003 allows you to create executable .mde files with all the references to the needed .dll's, however v2000 does not.

Should I just tell them to download the latest MDAC and install it?

 

[WayneRyan]

mathis,

You don't say what the errors are, but they are probably "user defined ...".
This is a references problem. A2000 does not include ADO as a default
reference. You can explicitly define it, when you build it, and you can
also programmatically set a reference to ADO when the app opens. EVEN
if you have to go find it in code.

Here's to a more stable future for apps,
Wayne

 

[mathisjay]

Thanks for the response. What I can't figure out is why the reference to Microsoft ActiveX Data Objects 2.1 Library IS set on the machine that I am building on, but not on the clients. I am opening up the v2000 database in v2002 and I can see the reference is checked. Are you saying that the box won't necessarily be checked on the client machine just becasue they are using v2000? How do I include the reference through code?

 

[mathisjay]

Here is the line is bombing out on

Dim rstRegionGroup As New Recordset

The error message is "Can't find project or library"

I checked with the client and the ADO 2.1 library IS checked on their machine. But when they try to compile the app, they get the error message.

I am stumped because I don't have v2000 to be able to test it on and see whats up.

 

[The_Doc_Man]

It is possible that some other reference is trapping you. See, Access is real good about kvetching that it can't find something. But oddly enough, it doesn't do so good about telling you WHAT it didn't find. If your customer is good enough to verify references are checked, have that person look for any other references that might be missing.

Also, just because it worked on A97 doesn't mean the file didn't move when they went to A2K. You might have to have them find the correct reference by browsing for it. A97 and A2K have different folder structures because of the extra security implemented in A2K. So one of the referenced files might be elsewhere.

Also, be aware that the DAO library is still important, but they changed names on it from A97 to A2K. A97 was something like DAO2535 but in A2K it has changed to DAO36 (or something like that).

 

[Kodo]

sounds like they don't have the proper MDAC.

http://msdn.microsoft.com/data/mdac/default.aspx

has a list of MDAC's. You may have to install 2.1 on that machine for it to work.

I would, however, suggest updating yourself to 2.8.

History of changes in ADO from 2.5 +
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdmscwhatsnewinado.asp

 

[mathisjay]

Just out of curiosity, if the client were to upgrade to v2002 or v2003 so that I could just send them a compiled .mde version, would this solve the probelm with the references?

It is my understanding that a .mde contains everything needed to run the app. Correct?

 

[mathisjay]

Doc Man-

You may be on to something.

I asked the client and sure enough, there is another missing reference. In my application I have a reference to Microsoft Office 10.0 Object Library so that I can use the FileDialog object. On the client machine, the referecne is missing. I asked the client to uncheck this reference and check the one for Microsoft Office 9.0 Object Library, but it still wont compile. Still gets the same error. Strange that it bombing out on the line containing the Recordset object and not the FileDialog object.

 

[Kodo]

Just out of curiosity, if the client were to upgrade to v2002 or v2003 so that I could just send them a compiled .mde version, would this solve the probelm with the references?

It is my understanding that a .mde contains everything needed to run the app. Correct?

this would solve the problem. All the office references would be the same version or atleast be available. As for the MDE, yes, it is the same thing as the MDB only the VBA code is compiled into p-code and can't be modified. So you can't design any forms or reports.