MS Access accde hangs up on system

I guess the quick and dirty solution is to uninstall everything related to Office
Just Uninstall them via control panel ...and then run the Remover Tool to clean the remnants.
If you want to be on the safe side take a full image of the system.

At least to my knowledge a 32 bit Access won't work on 64bit Access...just yesterday i stumbled on this on a client's machine
It's Greek but essential it says that in order to run this Access that was created with Access 32 you need 32bit Access

Well i must admit i haven't done this test...i reckon that as long the 32bit Access is "confined" on its own it would be just fine...i am not sure when you have Automation between 32bit and 64bit...

Bill,

<<The Access application locks up frequently. >>

 Could you go into this a bit more?   Are you seeing it just hang, or getting errors?

<<This client has installed Office 2016 64-bit without Access but including Word, Excel and PP.  They left Access 2010 on the system. >>

  I think I would have them go the other way; remove Access 2010 and run A2016 even though 64 bit.

  As Scott said, most apps will run fine.   However if you've used any API calls, you'll need to fix those for 64 bit.    Also you will have to distribute an accde compiled with 64 bit since .accde's cannot be recompiled on the fly.

@Scott and John:

  For Access 2010 and 2013, you could not mix 32 and 64 bit versions of Office.   Starting with A2013, many of the libs were shared.    I don't know if A2016 has changed in this regard or not, but I would suspect not.

  As far as I know, it's only with A2007 vs 2010,2013, and 2016 that you can have a different bitness and have everything work correctly.

  Up until A2013, it was always said that you only needed the same bitness within a single major version (ie. A2007 and back could be 32 and A2010 could be 64 without issue), but apparently 2013 used a lot of the same lib names as 2010, and this broke that rule.   To add confusion to everything, Microsoft continued to state that after 2013 came out, but that appears not to be the case.    I'll try and find out if this is really true or not, but from real world problems, that seems to be the case.

   Certainly a mess which ever way you look at it.

Jim.

My recommendation would be for you to uninstall the 64 bit version of office from the one computer and install the 32 bit version instead.  Even Microsoft suggests not to use 64 bit office unless you need Excel's really large number capability.

Dale

Hi All,  Thanks for the comments and the help!

The application hangs during search and data entry several times per day and is very slow compared to other installs at other locations.  Mostly during search.  We've rebuilt the data MDB (not ACCDB) data file on the server and rebuilt and recompiled the application.  We cannot flip the front end accde to AC64 bit since we use FMS Total Access Memo and there is no 64 bit version.

The IT folks steadfastly refused to install 32-bit unless I can assure them 100% that that's the issue.

Thoughts?

Time to do some science to prove/disprove the hypothesis

The IT folks steadfastly refused to install 32-bit unless I can assure them 100% that that's the issue.

Well as Dale said, Microsoft itself still recommends 32 bit:

https://support.office.com/en-us/article/choose-between-the-64-bit-or-32-bit-version-of-office-2dee7807-8f95-4d0c-b5fe-6c6f49b8d261

 
 32 bit installs is still the default as with 64 bit, there are very few advantages and a lot of downside.

 as far as the other comments I made, I am checking with others and Microsoft if mixing bitness across versions is really an issue or not.

Jim.

Hi Jim,  Thank you for any help from MS.  This has become a real pain...

Latest update is that IT has agreed to move to 32-bit Office 2016.  Does it make sense to convert the back end MDB to an ACCDB or ACCDE?  Will that provide any benefit?  All the back end has is tables and data.  This app has been in use since AC2000 days.

Thanks for your help!

Bill

Hi Dale,

I have about 25 sites that I would need to change or I would need to have different FEs for those with accdb and mdb so it will be a major undertaking in time for me.  What is the difference/benefit of ACCDB over MDB for the back end?

Thanks,

Bill

Does it make sense to convert the back end MDB to an ACCDB or ACCDE?

 It depends.   If your using work group security, then no, not until you can replace the security (the conversion will strip out the security).  If you don't know what I'm talking about, then don't worry about it.

 Also, unless your using some of the newer data types, then there is no difference really.  the ACE database engine is nothing more than JET 4.0 with some tweaks.

 At some point though, you will want to bring it forward.  

Jim.

OK.  I'm going to wait on this as it's working OK everywhere else and max 100k records or so.  Our latest version uses SQL.  We removed access security long ago.  

I'll check back when the users have given it another shot.

Thanks to all for your help in "making the case".

Bill

Hi Jim,  Good point!  Again, thanks to all.  Will close this question once I get feedback from my favorite IT folks.

So - latest is that all works OK after removing 64-bit Office, removing Access 2010 and compacting mdb file.  Seems like the Access 2010 search was trying to use the 64-bit component.  Anyway, thank you all for the help!!!

Bill