Re: Different version Access

Tech-Archive recommends: Speed Up your PC by fixing your registry

Your link helped me to get rid of that "Can't find project or library"
message yesterday; it was very helpful. Thank you so much!!!!

Let me recap your message to make sure I got it right. As for the
"decompile" process, is the command prompt the same as the "Start, Run" and
copy the code you gave me? And when I change to work on a different computer
at work, i notice there is always on reference missing, control 1.0 something
like that, so i have to Shift Open the file run the Module, and uncheck the
missing reference. Do I have to go to all users desktop to make sure I
uncheck them so it wiill run correctly? Is there a way I can put a error msg
box instead having the access showing my users with VBA code page.

By the way, what are those projects or libraries for?

Thank you so much! I couldn't have gone this far without all the helps I
received from this site.

Allen Browne wrote:
There is no software that can automatically handle the differences between
references on different computers.

There are many thousands of libraries. If one is not present, the software
cannot know how to simulate that library. It cannot even handle different
versions of the same library.

The solution, therefore is to limit the libraries you use. The Access and
VBA libraries are required. Access will automatically select the correct
Access library when you switch versions, so you don't need to worry about
that. You probably want the DAO 3.6 Library also, but it is also standard
across Access 2000, 2002, and 2003, so there is no problem with that either.

If you want any others beyond those 3, it is your responsibility to ensure
that the correct version of the correct library is correctly registered on
each computer where you will use your software.

More info on libraries for each version of Access:
http://allenbrowne.com/ser-38.html

Aside from the library references, there are some other issues that arise as
you change versions. An MDB contains 2 versions of your code:
- the compiled version (what executes);
- the text version (what you view and edit.)
The compiled binary is different with every version of Access. So, when you
edit an MDB using different versions, Access is supposed to re-generate the
binary for the current version from the text. That process is flawed, and
you tend to get weird errors that make no sense and can be inconsistent. The
solution is to explicitly decompile the database whenever you switch to
developing on a different version.

To decompile, make a copy of the database, and enter something like this at
the command prompt while Access is not running. It is all one line, and
include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

I have a database and experiencing some version reference problem. I
created
[quoted text clipped - 10 lines]
before,
so please help me to explain it in a simple language if possible.

--
Message posted via http://www.accessmonster.com

.

Relevant Pages

  • Re: Access 2003-Access 2002 Incompatibility
    ... Microsoft ActiveX Data Objects Recordset 2.7 Library ... The first one corresponds to msado15.dll (and adds the ADODB reference), ... There are two ADO type libraries. ...
    (microsoft.public.access.conversion)
  • RE: Built in function errors.
    ... Control reference, ... updating the software on the client computer and reselecting all ... reselect libraries simply makes the application not worth building using ...
    (microsoft.public.access.modulesdaovba)
  • Re: DB not working on other computer
    ... problem is fixed when I install Service Pack 1. ... referenced to regarding libraries and their relationship to projects. ... calculated controls if there are controls that contain expressions" ... > A "Missing" reference means that the files needed for a specific library are ...
    (microsoft.public.access.gettingstarted)
  • Built in function errors.
    ... TLBs on the client computer. ... reselect libraries simply makes the application not worth building using ... reference setup after resetting the references on the same computer. ... - Do not reference controls to use a value in automatic calculations on ...
    (microsoft.public.access.modulesdaovba)
  • Re: Are Cyclic dependencies allowed in file references?
    ... I can see how I can apply refactoring to eliminate the ... What guidelines can you share with me as to how to package class libraries ... > doesn't need to compile with a reference to the outside class... ... >> into building but it seems like I have one mysterious dll with an old ...
    (microsoft.public.dotnet.general)