MS Access 2000, Practice Solutions by Thomson Company, help migrating

This is a long shot but I have a client that needs to migrate a legacy MSAccess 2000 application from an old server to a new server.
The software "Practice Solutions by a Thomson Company" was purchased by a new company and they stopped legacy support years ago.
Even if I use the old computer name and identical shares, the program errors after it accepts the username and password.

The program icon "Practice Solution" runs this:
"C:\Program Files (x86)\Microsoft Office\ART\ART\Office\MSACCESS.EXE"  /runtime  o:\wincsi\PS\PSStart.mde

It then accepts the username and password but gives this error:

Error occurred in Init: finish_init: Initialize toolbar
Error 5: The toolbars need to be reinitialized, please restart Practice Solution.
{Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.}
(Source: gray_em:Microsoft JET Database Engine)

Anyone know a way around this?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jeffrey CoachmanMIS LiasonCommented:
Since this is an .MDE file, will need access to the original .mdb file.
So you will have to do all that you can to get info on the originating .mdb file.

See if any company took over Thomson, ...see if any vendors out there might support Thomson.
Ask present and ex-employees if they might know anything about the previous application's setup.
Make sure the MDB file is not buried somewhere in a rogue folder/drive, ...or in an old backup somewhere. (check with your Networking team)

Also note that there have been a lot of changes in Window as well as Office since 2000.
So there may be even more issue lurking...

If you can't get to the original mdb file. Then your only hope may be to just take the table data from the mde file and rebuild from scratch...

Lets see what other Experts may suggest.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It is probably well past time for an upgrade.  If the current company can't offer an upgrade to a newer product, there are companies out there that will decompile an .mde and give you back an .mdb.  It won't be pretty, but you can probably figure out what the problem is and possibly convert to a newer version of Access.
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
Sounds like the references are messed up, which because it's a MDE, your not going to be able to fix directly.

Is the new server running Access 2000 or a newer version?

Are you trying to run this under terminal services?

Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

jinfeldPresidentAuthor Commented:
The server is running nothing. The desktops run the runtime Access 2000.
No Terminal services. Straight LAN to a mapped O: drive.
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
I'd agree this sounds like a reference issue. The "multi-step" error often means troubles with the ADO/MDAC version, and you'll be hard pressed to resolve that without knowing the particulars of the problem.

You might check the Event Viewer to see if any additional information has been reported there.
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<The server is running nothing. The desktops run the runtime Access 2000.
No Terminal services. Straight LAN to a mapped O: drive.>>

So did the clients change then?   I'm trying to understand the setup.    If you just swapped out the server, then it should run.

Can you give a little more detail on the setup?   Did the clients change at all?   was there an install package?  etc.   Doesn't need to be a book<g>, but if just the server was swapped, it should run.

Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
Also assuming this is a Access MDB file on the server, not SQL Server right?

jinfeldPresidentAuthor Commented:
Thank you all. Each of you helped me understand what I was dealing with.
jinfeldPresidentAuthor Commented:
I solved this by using a Windows 7 box, changed the computer name to match the old server name, added a share that was identical to the old share and accessed that share from another desktop that had the MS Access runtime Practice Solution installed. Once I had the program running, it allowed me to open another database (which was a clone of the original database) on the new server. However, the program still had something hard pathed to the old server (in one of those .mde files) so we just left that Windows 7 box running on the network doing that one task (offering the shared folder like the old server). Dumb, but it now works.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.