Can't find project or libray

[TallMan]

Good Afternoon,

I have a unique situation, however I think it is a relatively easy fix.

I created a text box on a form me.base_date that displays the date when you open the database. At the time of creation I had access 2003. I have since upgraded to 2007 and made some changes to the database.....nothing catestrophic. In fact they were so small I did not bother to note the changes made.

Long story short. The users that are still working with access 2003 are unable to open my database without a "Can't find project or libray" error.

I have tried to check the microsoft 12.0 box under references but that did nothing.

I need to find a way that the associates can open the database without this error.

the code is listed below.

Private Sub Form_Open(Cancel As Integer)
Me.base_date.Value = Format(Date, "mm/dd/yyyy")
DoCmd.Maximize
End Sub

 

[MarkK]

1) I've had a similar problem that was solved by simply re-ordering references.
-> open a code window
-> goto: main menu->tools->references
-> select a reference and hit an arrow key to change its priority
-> click OK, distibute your app to a machine running 2003, and see if anything changes

2) Another possibility is the fact that Office products don't automatically reference earlier versions of themselves.
-> open your database on a machine running Access 2003
-> open a code window
-> goto: main menu->tools->references
-> set a reference to Microsoft Access 11.0 Object Library (I think. I've got Access 2007 and it is version 12.0. I presume 2003 is v11.0)
-> confirm that this solves the error you specified on that machine
-> distribute, test

If solution 2 works, note that machines running Access 2007 will automatically advance that reference, but not the other way around. Also, you'll need to introduce this step in deploying your work to 2003 machines.

 

[TallMan]

Lagbolt,

Thank you for the suggestions but it did not help.

To make sure I understand correctly.

For method one. I went into my 2007 code window and changed the priority of a couple of my references, then I went and checked the database on an associates pc with 2003. No luck.

For method two. I went to an associate with 2003 and looked at his references. He already had the Microsoft Access 11.0 Object Library selected.

I am lost on this one. These little glitches can really ruin ones day

To make sure you understand how I am testing it. The database is located in a share drive that all associates have access to. In order to test it I simply opened the db straight from the share drive. I did not copy and paste the db to their desktop. Also, I should be doing this in the front end correct? I have the database split as there are multiple users.

I dont believe the back end would allow me to access the references.


Thanks again.

 

[SOS]

1. Nobody should be opening the FE from the share. They should have a copy. ESPECIALLY with multiple versions going on. It shouldn't be done regardless but will be even more of a concern with more than one version.

2. Open a COPY on the 2003 desktop. Go to TOOLS > REFERENCES in the Code Window and go find the DAO 3.x reference that should be checked. If it is, uncheck it and close the dialog and then reopen it and check it again.

3. Restart the database.


Access 2007 uses a different DAO version than 2003. It uses ACE and not the old DAO 3.x.

See if that helps.

And every time you release you may have to fix it for the 2003 users. It really does depend on what you have there whether it will automatically work or not.

Also, make sure no references are marked MISSING as you would need to uncheck them and then close the datbase and restart.

 

[MarkK]

I agree with SOS here. You do an FE/BE split exactly because you don't want multiple users using the same file on the network.

 

[TallMan]

Thank you for your help SOS. I was not clear with my set-up. I currently have the "main" front end and back end on the share drive which I use to when updates are needed. Each Associate has their own copy on their desktop.

SOS - Your second option worked. The copy has to be on the persons desktop though. Not that it matters but as soon as I try to open it from the share server the same message is thrown.


"2. Open a COPY on the 2003 desktop. Go to TOOLS > REFERENCES in the Code Window and go find the DAO 3.x reference that should be checked. If it is, uncheck it and close the dialog and then reopen it and check it again."

What a strange fix....Access can be so delicate sometimes!!


Thanks again guys!