Access file migration from 2003 - 2007 Big problem

[ieronymous]

Hello


New one here, not a programmer but a technician with problem migrating an access file from win xp to win 10 x64 running office 2007.
I have a doctor client running this file, year ago. His pc is dying and with no hope to revive it he upgrated to a new one. I have managed
to migrate each other of his medical programs succesfuly other than that damn access file. In the link below you ll find a link to downlaod the
file im having problems with. I ve tried anything with the errors with no success. Anyone can help me with this ill be more than gradeful

Thank you in advance

PS I ve also attached additional dao files from the xp machine in case someone needs them.
Finally to mention ive followed probably all the solutions found in google (at least the first page results) with no success

http://s000.tinyupload.com/index.php?file_id=00411132152781701556

[ItsMe]

dao ?

This file may have been built specifically for that xp machine. What version of Access was being used on the XP machine? Can you look at the shortcut (the one used to launch the app) on the XP machine and see what files (and their paths) were used with the shortcut?

[ieronymous]

Well the microsoft office version was 2003 so i assume access was the same version also.
The file wasn't a shortcut but was running by the file itself so i suppose it was hard coded?
I have uploaded the file. Can't you download it?

Ps the initial error refers to missing dao350.dll then dao2535.tlb, then

[ItsMe]

...
The file wasn't a shortcut but was running by the file itself so i suppose it was hard coded?
...

Well, that is good news. The bad news is that you will need an older version of Access to open the file. At least, older than the version I have at my machine now. Access 2013 does not play well with MDB files. Access 2007 should be able to open an mdb. However, I do not believe it can open a 2000-2002 file format of mdb. This may be the issue right there. The fact that there are separate support files leads me to believe the version you have is uber old (pre 2000) and you will need an XP machine with Access 2003 to convert it to 2002-2003 file format MDB. Then, using Access 2007 or later, it would be advisable to convert it to an accdb.

Make copies now.

[ItsMe]

Hey, those screenshots help. And make sure to make copies of the file. Like a copy that resides on the XP machine. Not a opy of a file that you tried to open with Access 2007, etc.

When you get to the message that says "Compile Error", see if you can click OK and get to the toolbar of that VBA editor window. The main window with the white background and says Visual Basic is what I am talking about. Click Tools>References and make notes on the References Window. The "Missing" references should be bold and at the top. Do not uncheck them. Make notes of what they say before unchecking them. You need to replace them with references to libraries that actually exist in that machine. Tell us what the missing references are.

The first error is because of a trusted locations thing. The fact that you have the Visual basic Editor open indicates you will be able to get past the Trusted Location issue. Also you can make an edit to the Machine's registry to get past the first trusted locations message thing. If you want to do the edit manually, I can offer some terms to google or, if that is a full version of Access, there should be a user interface to accept the risk. I have not tested the app uploaded in this post on W10 yet, but I use it on XP, W7, and 8.1. I use it on Access 32 bit. The 32bit version of Office/Access is installed by default. The app I uploaded here will automate the registry edit and add a folder to the trusted locations of Access.

[ieronymous]

Hey, those screenshots help. And make sure to make copies of the file. Like a copy that resides on the XP machine. Not a opy of a file that you tried to open with Access 2007, etc.

When you get to the message that says "Compile Error", see if you can click OK and get to the toolbar of that VBA editor window. The main window with the white background and says Visual Basic is what I am talking about. Click Tools>References and make notes on the References Window. The "Missing" references should be bold and at the top. Do not uncheck them. Make notes of what they say before unchecking them. You need to replace them with references to libraries that actually exist in that machine. Tell us what the missing references are.

The first error is because of a trusted locations thing. The fact that you have the Visual basic Editor open indicates you will be able to get past the Trusted Location issue. Also you can make an edit to the Machine's registry to get past the first trusted locations message thing. If you want to do the edit manually, I can offer some terms to google or, if that is a full version of Access, there should be a user interface to accept the risk. I have not tested the app uploaded in this post on W10 yet, but I use it on XP, W7, and 8.1. I use it on Access 32 bit. The 32bit version of Office/Access is installed by default. The app I uploaded here will automate the registry edit and add a folder to the trusted locations of Access.

Well i think i made it workkkkkkkk.........at least for the menus and tables!!!!! I dont know about the printings though because im home trying with 2007 version access. What i did was to encounter the first problem

Pressed enter several times and when promted to disable all macros I just pressed x. With alt+f11 went to an editor menu to tools/references and there were some missing link as you can see in the pic below


So i unticked the missing broken link and checked the DAO 3.6 Library. That passed the first error message and now when i open the file goes directly to TheDOMenu action cannot be run in disable mode. If i press ok and tehn x to the next box and go to security warning / options / enable thiscontent (see below) it opens



No i need to bypass the 2358 error and open the menu directly. Any ideas?

[ItsMe]

That missing Reference is baked into newer versions of Access. And, I think 2007 use the JET database engine. So there is no need to reference DAO 3.6. I would uncheck DAO 3.6 and then attempt a compile. You will use DAO 4.0, which is baked in.

In the Menu Bar, next to Tools, is 'Debug'. Click Debug>Compile Database. If the Compile Database is greyed out, edit some VBA. You do not need to change any code, just add a line by clicking somewhere in blank space and hit Enter on your keyboard.

The idea is you want to compile the VBA to make sure there is not any conflict the existing code. It is not an answer to everything, you can still encounter Run Time errors. But. it's a start.

[ieronymous]

I ve added trust credencials to the path of the file and now it opens directly to the menu.

[ieronymous]

Well it was in different place the Debug / Debug test did nothing just greyed out and even if i close the file and re open it still greyed out. If you can, i have uploaded the file, grab it and run the tests you mention cause i dont know

Thank you

[ItsMe]

That's sounds good to me. The point is not whether or not Compile Database is greyed out when you first open the database. The point is to Compile the VBA code. In order to compile the code, the option needs to be available. So, if it is greyed out make it available by adding white space to the VBA where there is already some white space. Then, run the Compile Database tool. Editing the code will enable the Compile Database.

So, if it is enabled and you click it, one of two things will happen. It will show you where a compilation error is or it will do nothing. Actually, doing nothing is equivalent to changing from Compile Database enabled to Compile Database disabled.

The only thing left to do is test the Access file during Run Time. So this means working with the DB. If you have a copy, you might try opening forms and fumbling around. However, the only real test is actually using it.

.

[ieronymous]

Thank you As about the testing i ll let client do it and report me the errors he ll encounter. As for the compile i dont have time now but ill give it a try at night

[ItsMe]

Sounds good. After it is determined that the code used within the application does not produce any Run Time errors, it is advisable to use Access 2007 to convert this application to an accdb (the newest version possible using Access 2007).

[ieronymous]

Sounds good. After it is determined that the code used within the application does not produce any Run Time errors, it is advisable to use Access 2007 to convert this application to an accdb (the newest version possible using Access 2007).

By the way do you have a guide for that... i dont use access at all i just tried to help my client.

[ItsMe]

As you mentioned, the End User can determine if the existing code will generate a Run Time exception. It is not the ideal thing. You could set them up with a copy and ask them to pretend they are working. it is not fun when you get an unhandled Run Time exception in a production environment.

But, upgrading to an accdb should be rather simple. The caveat is, upgrading may create new issues. In other words, the current databse you have may rely on features that have been deprecated and no longer supported by Access 2007. This is why I recommend testing the existing version in Run Time. If there is a problem, you need to be able to distinguish if the problem is caused by the accdb conversion or simply from Access 2007 and the new machine interacting with the mdb.

The only real issue I might be able to predict would be if the current mdb file uses User Level Security. If, when the database opens, you are not prompted to login as a specific user and there is not a separate mdw file associated with the mdb, the database is not using User Level Security. Having said that, ULS is deprecated but Access 2007 can still interact with it. It is accdb that does not like ULS.
https://support.office.com/en-ca/art...3-2f3eafa904a5

I am not positive what the GUI looks like in Access 2007 when creating the upgrade from mdb to accdb. I googled and found one explanation how. It seems Access 2007 will automatically look for 97 format (pre - 2000). So I would start your venture with the beginning of the explanation in this link. Then, follow the prompts. Just be aware the Wizard may throw in some extra steps (Database Enhancement) if it predicts Access 97.
https://support.office.com/en-us/art...0-f790fa9f359c