Access Runtime and Excel 2003 VBA

Hello All

I have an odd issue here.  I am not even sure if it is an issue because a user is claiming their Excel VBA stopped working EXACTLY when I installed Access 2013 runtime.  I have learned that "sometimes" users are not correct :D (Hey but who knows, he might be right)

I installed Access 2013 runtime on all the computers here so that the users can run an Access database.  One user, who uses Excel 2003 and has created many controls with VBA/macro code behind them, now cannot activate any of the controls.  Buttons that used to click and produce a result now will not click (it is as if they are not even there).  When he tries to put in another object (like another command button) it will not allow him to insert the object.

I did some looking and I found something dealing with a Microsoft patch that knocks out the VBA/macros.  I deleted the exd files but it still does not work for him.

Could Access 2013 runtime have effected Excel 2003?  I have uninstalled Office 2003 and put it back on as well as uninstalling Access 2013 runtime and reinstalling.  Same error.

Any ideas?

Thanks
alevin16Asked:
Who is Participating?

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

x
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.

Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<Could Access 2013 runtime have effected Excel 2003? >>

 Yes.  Access as part of Office, runtime or not (which is nothing more than the full version with design features disabled) can impact one another because they share a lot of Office components.

 In addition, with 2010 and up, there is a 32 and 64 bit edition of Office and you cannot mix and match (32 bit Access, 64 bit Excel and everything else).

 I would un-install both, then install Excel alone again.   Then take a look at what version of the run time your trying to install (32 or 64).

 Jim.

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
Rey Obrero (Capricorn1)Commented:
-note:
after uninstall of the Offices, REBOOT your computer, before installing Office again.
gowflowCommented:
I would simply do this:
1) goto Control Panel
2) Choose Programs and Features
3) Locate Microsoft Office 2003 and run a repair on it.
4) Once done reboot the pc and try if problem solved.

gowflow
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

alevin16Author Commented:
Hey All

Thanks for the comments.  I did install only the 32bit runtime (in fact when I accidentally tried to install the 64 bit, by clicking on the wrong downloaded file, the computer yelled at me).

Repairing did not help.  I tried that first and it still had the error.  

One other thing I just tried, I copied one of the excel spreadsheets that he was using onto my computer.  I have office 2013 full version.  I was able to open and run he macros/vba code.  It seems to only effect the office 2003 users (I wish I could update those machines but they are connected to very specific machines that can only be controlled with a computer running office 2003).

I will try to get some screenshots so maybe that could help.

Thank you all very much again!
Andy
Boyd (HiTechCoach) Trimmell, Microsoft Access MVPDesigner and DeveloperCommented:
Any,

After you uninstall the Access 2013 Runtime (Leave Office 2003),  have your tried god back to a  restore point that is  before the Access 2013 was installed? That mare rest it.

TIP: Making a System Restore point before installing anything can save you if there are issues.

I would avoid missing versions of Office apps. Access runtime included. When I deploy my Access app to clients that do not have Access I use the version of the Access runtime that matches there version of office. This eliminates any compatibility issues.

I have found Office 2013 not to play well with prior versions when installed side-by-side in the same  Windows instance.  II will use a VM, Termainl Serice  or RemaoteApp to avoid installing Offie 2013 apps with any othwr version of Office apps..

If the Access database that needs to be run will work in Access 2007 then I would try the 2007 runtime.
alevin16Author Commented:
Hello Boyd

we actually restored the computer using an image we took before we ever installed Access 2013.  The computer worked fine.  It seems that after Access runtime is installed whatever it effected stays effected.

I am going to try restoring another computer and then put Access 2007 runtime (is there even such a thing? :)  )   I don' think my program will work though without at least access 2010 runtime.

I'll keep everyone posted.

Thanks for the ideas!
Andy
Martin LissOlder than dirtCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
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 Excel

From novice to tech pro — start learning today.