Tools

What if OneSource will not open up using Access 2007 or Access 2010 (on the first try)?

Author: Steve Childs Reference Number: AA-01609 Created: 2011-04-09 09:10 Last Updated: 2011-04-19 17:07

0 Rating/ Voters

Broken or Missing References?

When OneSource (which is developed in Access 2003) is opened in Access 2007 or Access 2010, OneSource (Access) needs to change the Code Libraries (DLLs) to newer versions of the DLL's and/or link to versions of the files that are stored in different places, depending on the operating system (32bit, 64bit, etc). This can typically happen AUTOMATICALLY--IF--the system is given the rights to do this. (When you open Access 2010, even if the user who is logged in is an administrator, it does NOT give Access the permission to make the changes to the references). To GIVE Access the rights, you will need to follow these steps on the first login of OneSource:

Prerequisites:

On the original Dev environment (on Windows 2003/Access 2003), open up copy of code (Ctrl+G) and remove all references except Visual Basic for Applications, Microsoft Access version x Object Library, and the Microsoft DAO 3.6 Object Libary--so there will be fewer conflicting references on the other/newer server/version of Access).
Make sure the copy of OneSource.mdb that you have downloaded has the osShow option turned on (so all objects are immediately visible when you open up OneSource).
After downloading, place this copy of OneSource in the typical place that you would store a copy of OneSource for the osadmin.

Next, browse to the MSAccess.exe file (usually located on a Windows 2008 Server here: "C:\Program Files (x86)\Microsoft Office\Office14\MSACCESS.EXE" (it will be the same path but Office12 for Access 2007)) and right click on it and select Run as Administrator. (This opens up Access in Administrator mode).
Now, click on the Open option, on the left, and browse to the copy of OneSource.mdb in the OSAdmin folder that you want to set up.
Now take whatever steps you normally take to open the VB code editor. (Ctrl+G is quick and easy). You will more than likely see an hourglass at this point.
The next step is to be very patient...as it could take up to 30 minutes or longer for Access to scan and update the References with the proper .dll files for that version of Access. When it is finished it will either open up the code or the hour glass will turn off. (If it does not open the code, you may have to repeat this step, but it will open the code immediately the 2nd time around--since the References are now linked).
Once in the Code Editor click on Tools > References to view the new references. If any shown are [Missing] browse to the proper references and link them.
Next click Debug > Compile. If all references are in place it should compile without any errors. (If not, it will stop on the exact code that has a reference to a function or object that it cannot find. If you have already made sure the proper references are in place, you may need to get additional help from a OneSource tech support rep or developer).
Next, use the osHide command to close OneSource and then re-open it and click on the 'Relink to a different Data File' button and link the tables.
Finally, you will need to use the osHide command to turn off menu changes and hide the Access tables.
NOTE: If you are doing this in reverse, meaning taking an Access 2007 or Access 2010 file from Customer X to open up on a Server 2003 (using Access 2003), then it is best to open up the code (on the original 2008 Server) and un-select all references that you can. This will make it easier to open up this file using Access 2003.

Incorrect User Security Rights?
Is there of lack of 'Trust' by Microsoft Access to execute source code in the folder that it is in?
Is the Company Data File not properly linked?
Is MSAccess.exe stuck in memory?