Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
Legacy Access breaks with Access 2015
I've got a very cherished version of Access 2k, I'm supporting a number of legacy apps with all the old toolbars, etc. All the good stuff which has gone....so I really need it...but I've just installed Office 2015 and to my horror Access 2000 breaks/ runtime exception.
Up till now, I've been able to run Access 2k with the later versions side by side...is there a way to continue?
Up till now, I've been able to run Access 2k with the later versions side by side...is there a way to continue?
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
First thing to do is ... open the VBA Editor ... Tools>>References
Look for any that show:
**MISSING <SomeReferenceName>
Resolve missing references if any.
If no missing References (unlikely) ... the Debug>>Complile
There will likely be some compile errors ... report back
mx
Look for any that show:
**MISSING <SomeReferenceName>
Resolve missing references if any.
If no missing References (unlikely) ... the Debug>>Complile
There will likely be some compile errors ... report back
mx
Either set up a virtual machine with an older operating system to run your legacy application, or else upgrade the application. Coexistence of Office was never the greatest idea.
No need for a VM really. I've run multiple version of Office on one machine for many years.
Although you may ... have some issues coexisting A2K with A2016 ... SO much has changed.
Although you may ... have some issues coexisting A2K with A2016 ... SO much has changed.
Actually, I think I panicked a bit early. I have got the old 2k running, its just the VBA code editor is behaving a bit strangely.. mmmm...its nothing very consistent to be easy to comment on...for the first time ever (I an remember) I'm getting the code window saying:
"Not enough memory to show window..."
"Not enough memory to show window..."
Hopefully Access 2016 went in a separate directory from A2000. If not, your going to need to un-install both, then re-install in order.
Jim.
Jim.
"then re-install in order."
Just to elaborate slightly ... Install A2K then A2016 *in separate folders*
However ... since A2013 no longer supports A97 mdbs ... It's VERY likely that >A2016 may not support A2K mdbs.
So ... at some point ... you will need to convert your mdbs to ACCDBs ... the sooner, the better.
Just to elaborate slightly ... Install A2K then A2016 *in separate folders*
However ... since A2013 no longer supports A97 mdbs ... It's VERY likely that >A2016 may not support A2K mdbs.
So ... at some point ... you will need to convert your mdbs to ACCDBs ... the sooner, the better.
Phew....its working now, strange behaviour at first, seemed to get better with use...weird.
Leave Access 2k, never! What about the toolbars? The use-level security?
What's really been added? The VBA is the same vintage isn't it?
The only thing I've actually missed is the ability to embed some text functions into SQL...but easy to work round.
Leave Access 2k, never! What about the toolbars? The use-level security?
What's really been added? The VBA is the same vintage isn't it?
The only thing I've actually missed is the ability to embed some text functions into SQL...but easy to work round.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial