Class Not Registered in MS Access Office 365

%3CLINGO-SUB%20id%3D%22lingo-sub-1320125%22%20slang%3D%22en-US%22%3EClass%20Not%20Registered%20in%20MS%20Access%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1320125%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20work%20colleague%20has%20a%20new%20laptop%20running%20Windows%2010%20and%20Office%20365%20Professional.%26nbsp%3B%20I%20have%20copied%20across%20an%20Access%20database%20(.mdb)%20that%20runs%20beautifully%20on%20my%20laptop%20that%20runs%20Windows%2010%20and%20Office%20Professional%202013.%26nbsp%3B%20The%20database%20opens%2C%20and%20functions%20well%20except%20when%20running%20a%20module%20it%20fails%20and%20returns%20the%20runtime%20error%20%22class%20not%20registered%22.%26nbsp%3B%20I%20have%20tried%20converting%20to%20.accdb%20and%20repairing%20Office%20365%20but%20the%20error%20persists.%3C%2FP%3E%3CP%3EI%20did%20not%20write%20the%20code%2C%20which%20was%20written%2017%20years%20ago%20and%20I'm%20not%20able%20to%20contact%20the%20person%20who%20wrote%20it.%26nbsp%3B%20I%20have%20attached%20the%20VB%20code%20in%20question.%26nbsp%3B%20The%20error%20occurs%20at%20the%20following%20(2)%20places%20in%20the%20code%3C%2FP%3E%3CP%3ESet%20GrpSvr%20%3D%20CreateObject(%22GrpSvr.GrpCall%22)%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20only%20difference%20I%20can%20see%20in%20our%20reference%20tools%20is%20that%20I%20have%20Microsoft%20Access%2015.0%20Object%20Library%20and%20hers%20is%2016.0.%26nbsp%3B%20We%20both%20have%20the%20Microsoft%20DAO%203.6%20Object%20Library%20with%20the%20same%20version%20of%20DAO360.dll%20installed.%3C%2FP%3E%3CP%3EAny%20advice%20is%20truly%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1320125%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1320566%22%20slang%3D%22en-US%22%3ERe%3A%20Class%20Not%20Registered%20in%20MS%20Access%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1320566%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F628463%22%20target%3D%22_blank%22%3E%40stokeslj%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFurther%20information%20that%20might%20be%20helpful....the%20new%20laptop%20that%20I%20am%20having%20problems%20with%20is%20running%20a%2064-bit%20version%20of%20MS%20Access%2C%20but%20on%20my%20laptop%20where%20it%20works%20beautifully%20runs%20a%2032-bit%20version%20of%20MS%20Access.%26nbsp%3B%20We%20both%20run%2064-bit%20operating%20systems.%26nbsp%3B%20Will%20uninstalling%20the%2064-bit%20version%20of%20Office%20365%20and%20then%20installing%20the%2032-bit%20version%20on%20the%20new%20laptop%20work%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1322587%22%20slang%3D%22en-US%22%3ERe%3A%20Class%20Not%20Registered%20in%20MS%20Access%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1322587%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F628463%22%20target%3D%22_blank%22%3E%40stokeslj%3C%2FA%3E%20I%20actually%20recommend%20(particularly%20since%20this%20is%20old%20code)%20that%20you%20start%20by%20trying%20to%20comment%20out%20the%20procedure(s)%20where%20this%20code%20is%20called.%26nbsp%3B%20See%20if%20the%20code%20compiles%20without%20them%20because%20it%20is%20possible%20that%20it%20is%20no%20longer%20used.%26nbsp%3B%20That%20way%20you%20do%20not%20waste%20time%20on%20this%20issue%20unless%20you%20have%20to.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1326536%22%20slang%3D%22en-US%22%3ERE%3A%20Class%20Not%20Registered%20in%20MS%20Access%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1326536%22%20slang%3D%22en-US%22%3EThanks%20Maria%2C%20I%20tried%20your%20recommendation%2C%20but%20i%20still%20have%20the%20problem.%20I'll%20keep%20searching.%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

My work colleague has a new laptop running Windows 10 and Office 365 Professional.  I have copied across an Access database (.mdb) that runs beautifully on my laptop that runs Windows 10 and Office Professional 2013.  The database opens, and functions well except when running a module it fails and returns the runtime error "class not registered".  I have tried converting to .accdb and repairing Office 365 but the error persists.

I did not write the code, which was written 17 years ago and I'm not able to contact the person who wrote it.  I have attached the VB code in question.  The error occurs at the following (2) places in the code

Set GrpSvr = CreateObject("GrpSvr.GrpCall") 

 

The only difference I can see in our reference tools is that I have Microsoft Access 15.0 Object Library and hers is 16.0.  We both have the Microsoft DAO 3.6 Object Library with the same version of DAO360.dll installed.

Any advice is truly appreciated.

4 Replies
Highlighted

@stokeslj 

Further information that might be helpful....the new laptop that I am having problems with is running a 64-bit version of MS Access, but on my laptop where it works beautifully runs a 32-bit version of MS Access.  We both run 64-bit operating systems.  Will uninstalling the 64-bit version of Office 365 and then installing the 32-bit version on the new laptop work?

Highlighted

@stokeslj I actually recommend (particularly since this is old code) that you start by trying to comment out the procedure(s) where this code is called.  See if the code compiles without them because it is possible that it is no longer used.  That way you do not waste time on this issue unless you have to.

Highlighted
Thanks Maria, I tried your recommendation, but i still have the problem. I'll keep searching.
Highlighted

@stokeslj 

The solution was uninstalling the 64-bit version of Office 365 and installing the 32-bit version.