Running MP2 Access 2000 on Windows 7 64-bit August 9, 2013
Posted by wackytheadmin in Technology, Windows.trackback
This is entirely possible and even the MP2 website says it’s possible, you just have to contact them for the “fix” and then they want you to pay for it. Well fuck that. Here’s what I did, and it worked. I copied the entire MP2 folder from the Program Folders on the old PC to the new one. I found ddao36.dll in the original installation source and copied it to C:\Windows\SysWow64. Opened a command prompt and did: cd \windows\syswow64, then: regsvr32 c:\ddao36.dll. Cleared the “error” that popped up (I don’t recall the verbiage ATM), and created a shortcut on the desktop to the MP2.exe file. Double clicked it and BAM! Hopefully it works for you too and you can save some cash.
You can thank me later,
Wacky
The Wacky Admin 
I keep getting an INI error. Followed all steps to the T.
Hey Rob, follow Karen’s comment and look at your shortcut and the ini file. Thinking back, this is something I had to do as well. I no longer have access this PC as I have changed jobs. Glad these worked for you and sorry for the delayed response. I didn’t realize I had to moderate the comments.
Thanks Wacky! I am going to try this
This worked for me, I thank you. The only proble I had with mp2.exe is that it pointed to mp2.ini, which was not in the folder. Looks like it is supposed to be mp_2000.ini. I copied the shortcut from the old computer – which reference the other ini file and it works great. I could have changed the name of the ini file as well.
Thanks Again!
Karen and Wacky, is there anything else because I was not able to connect to the database.
I copied MP2 in C: \ Program Files (x86) \ MP2ACC2000, create ODBC 32 (C: \ Windows \ SysWOW64 \ odbcad32.exe) refers to the C: \ Program Files (x86) \ MP2ACC2000 \ mp250prv.mdb, I checked the ini file and seems to be fine and shortcut points to mp2_2000.ini. I copied and ddao36.dll and registered the dll.
When I start the program, there is error “Open Dummy Record” and in the next window “Unable to login into database. The database server may be down.”
Did I miss something or made a mistake in some steps?
Thanks in advance.
Wall
I’m not sure on this and I have no way to check, as I don’t have access to the PC I did this on. Maybe Karen will see this and respond.
Wacky,
Thank you very much for your response, I thought you might remember that you had a problem when switching databases.
Thanks anyway.
Dragan
We have our MP2 located on a network drive, so this is likely to be slightly different, but you’ll get the gist of it:
1. Open Notepad elevated (right click, Run as Admin)
2. Open mp2_2000.ini
3. Change anything that references C:\Program Files\MP2ACC2000 to C:\Program Files (x86)MP2ACC2000 (for me, this was 2 locations – “Private Path” at the top, and “Image” a bit over halfway down the file)
4. Our data path is mapped directly to a network drive letter, so if yours is strictly local, this may need to be changed to reflect the (x86) addition as well.
What was interesting to me is this actually works even without defining the ODBC’s on the x64 computer, presumably because the ODBC is already defined in mp2_2000.ini.
This has been tested on Windows 7 x64 with Office 2010 Standard, and Windows 8.1 x64 with Office 2013 Professional. Both worked exactly the same way.
I have this working on winndows 7 machine, but having trouble printing built in reports – for instance work order report – the report name is [untitled] – it must generate from within the system. Reports that we have created work OK. So if I open work orders, click a line item and click print preview – the first message I get is “cannot access SQL server” The next time I click print preview – I get error message cannot connect to database, invalid password, I cannot preview or print individual work orders.
Some of the other built in reports will work – like the inventory – I can pick a line item and print preview\print this.
Any ideas?
i have the same issue. App is installed and running per the instructions above, but I cant seem to get printing working for anyone. Anyone have any suggestions on this? We are running the access 2000 version of this, predecessor to the sql versions. Help!?
Hi Karen (and anyone else with this problem). I know it’s been a couple years but I have a solution.
I had the same error when printing. After doing a little digging, I noticed that the software creates ODBC connections on it’s own. Unfortunately, the connections are made in the 64-bit section of the registry. If you fire up REGEDIT and navigate to HKLM\Software\ODBC\ODBC.INI you will find the MP2 Connections.
I exported the ODBC.INI key, opened it in my favorite editor (N++), deleted all unneccesary keys, and did a “Find and Replace” (CTRL+H) to replace all “Software\ODBC” with “Software\WOW6432Node\ODBC”
Import the corrected reg file, reboot, print.
I have done the setup as described above. The application prompts for the users password and then nothing happens. If you type an incorrect password it knows that it is incorrect so I can see it is reading settings from somewhere. I ran into many of the issue stated above, error opening dummy record etc. and have overcome. Now there is no error message and nothing in event viewer, it just disappears without a trace after typing the correct password.
I figured it out! MP2Access2000 is finally working on Windows 7×64 after more hours than I should have spent spread over several weeks. If you have done all steps above and it is still not working go to where the database is stored, open the .mdb (it may be password protected but easy to crack, ours was “mp2”) and do a Compact and Repair. Good Luck!
How did you overcome the error opening dummy record? I have tried all the suggestions on this page and nothing will fix the dummy record issue.
How did you overcome the error opening dummy record? I have tried all the suggestions on this page and nothing will fix the dummy record issue.
After everything I went though to get this application working there were still several features which would not work. We ended up contacting infor and upgrading to their new product. If I were you I wouldn’t put any more time into it and just start looking into another product or the upgrade from infor. I do not remember what I did to get past the error opening dummy record except that I wasted way too much time on this.
Thanks Chris.
This may be slightly off the subject, but I can successfully install MP2 Access 2000 on a Windows 8.1 32 bit tablet and play around with the training database. I can print reports to Adobe (I don’t have a physical printer installed). I did receive the following error during installation “The procedure entry point HttpOpenDependancyHandle could not be located in the dynamic link library C:\Windows\System32\urlmon.dll”. I received that error numerous times but clicked through it. I realize this doesn’t resolve the 64bit issue, but might be a way for some to extend the life of their MP2 Access 2000 system without incurring a huge expense. Set it up on a dedicated computer and access it via remote desktop (I hope Windows 8 allows that, I worked with it a lot in XP).
or buy an Windows XP SP3 machine off e-bay and access it via remote desktop. Set it up with a dedicated printer. It’s a real shame to have to spend the money to upgrade to MP2 6.1 SQL (which Infor really doesn’t advertise although some say you can still purchase it).
I am still using this with windows 7, am getting the error opening dummy on 1 user, all the rest are OK. SO this has to be related to the user somehow. looking…
I have this working on a Windows 7 x64 machine accept print wont work, error says: MP2 cannot find the report template file WOPRINTL.rpt.
Any suggestions.
Sorry to revive this old topic, but….
Poster #10 Karen, I’m having the same issue. Were you able to resolve this?
The combination of posts above led me to successfully installing the MP2 client on a Win 10 x64 PC. The DB resides on the network. Reports and printing are functional too. Here’s what I’ve gathered:
1. Copy the MP2ACC2000 folder from the old PC into C:\Program Files\ on the new PC (NOT the \Program Files (x86) folder. If you put it there, you’ll need to edit the INI file and possibly other unknown areas).
2. Copy the ddao36.dll file from C:\Windows\System32 on the old PC into C:\Windows\syswow64\.
3. Open a command prompt (elevated): cd \windows\syswow64 hit enter then: regsvr32 c:\ddao36.dll and hit enter
4. The error that will appear is: the module failed to load. the specified module could not be found. Select OK. (based on this error, I’m not positive that steps 3 and 4 are necessary, but I did it anyways).
5. Copy the MP2 shortcut from the old desktop to the new one. Right click – Properties. If you see “(x86)” in the path of the target, delete it (since you put it in the regular program files folder). Hit apply and OK. MP2 should run at this point, however, it will be very slow to login. As noted above, this seems to occur because it’s using the ODBC info in the ini file to manually create the ODBC connection each time you log in. Why it’s slow, I don’t know, but the fix is to import or recreate the ODBC info.
6. On the old PC, export the registry folder HKLM\SOFTWARE\ODBC\ODBC.INI. On the new PC, import that registry file. Now, MP2 will login at a normal speed.
I am trying to install this on another windows 7 machine and am getting Exception EAccessViolation in module MP2.exe – anyone else get that?
I have the same EAccessViolation error – Anyone else!?