Getting help and advice from one of the many experts here at Microsoft Community does not cost anything.
Whenever you receive a phone number as an answer and feel uncertain whether it is from someone at Microsoft, don’t take the risk,
confirm the number is for official Microsoft Support.
Glad to hear the hotfix has been working.You should be able to install the hotfix with either a /quiet or a /passive switch.I believe a /quite will be a completely silent install of the fix and a /passive will be an unattended install and will only show a progress bar.To see these options you could open a run command and put the path to the hotfix .exe file followed by a /?
This hotfix has not worked for remote users. Any idea when MS will be fixing Access?
Remote users are getting blank forms instead of the bound data for a sub-form in datasheet view.
If I compile exactly the same application in Access 2007 the app works fine, if i compile it in 2010 SP1 (with or without hotfix) the app doesn't work for remote users, but in-house users it is running fine?
Is there any other hotfix which will resolve this once and for all?
EDIT: I have also found that after binding a DAO.recordset to a form, as soon as you start to try to appy a filter, the DB crashes and no amount of DECOMPILE is resolving this?
To err is human, to really balls things up you need Microsoft!
As mentioned above, unfortunately, this hotfix won’t fix all crashing issues with Access or issues with blank forms.It is intended only to fix the issue in KB 2625046.If you are experiencing other types of crashes or errors, then you may want to open up a ticket with Microsoft so we can look at this specific crash with you or start a new thread on this
forum for your specific issue.
So I now have shortcuts on my desktop to each of our DB's with the /DECOMPILE switch so when ever I open a DB it is decompiled before i work on it.
I'm not sure if this is a good idea. Almost every resource on the web talking about the /decompile switch tells you to make a backup copy before. It's an undocumented feature which might not have received production level testing. The following usenet post
contains additional information about the background of the /decompile switch:
You are correct, you should make a backup copy of the database before using the decompile switch.With that being said, it was a temporary workaround and now that a fix for the issue is available, I would recommend installing this fix and using it going forward.
First of all, thank you for paying attention throughout this blog. It has proven to be very, very helpful.
I am attempting to update and repair Access 2003 db to Access 2010. Eventually there will be SQL tables.
I have had nothing but issues since the update. I love working with 2010 but the crashes have made me look real stupid to my bosses. So far I've had a Just-In-Time debugging error that I finally repaired by removing all files related to Visual Studio. Now I'm
having the crash mentioned throughout this blog.... FYI.
Tonight I'm going to attempt the hot fix. Wish me luck.
Question... have there been any further updates available that will fix this crash? I've searched and cannot find anything. I just need to know if there is something I need to do beyond this hotfix. I've got an IT guy coming tomorrow and a full team at my disposal
when we are ready to upload onto our new network at the factory. I'll need to give them as much instructions as necessary prior to bringing 15 users on line.