Many of us have encountered the problems with continually having to decompile
Dbs after applying SP1. Has the problem been fixed, and if so, what is the
correct patch as there seem to be so many hot fixes? I am running Windows 7
64 bit and Access 2010 32 bit

Thanks

Phil

On Nov 22, 3:28*am, "Phil" <p... (AT) stantonfamily (DOT) co.uk> wrote:
Me, XP/32 bit.

As near as I can tell Access 2010 is extremely unstable. Decompile
sometimes works, sometimes doesn't. It constantly crashes when
opening anything dealing with VBA Perhaps it's MS's subtle way of
moving developers from VBA into macros.

Access 2010 is a pretty program. As one manager said to me many years
ago "I prefer an ugly program that works to a pretty program that
doesn't."

For those of you unfamiliar with the A2010 feature...one designs some
tables and forms with some code and some modules. Works like a
champ. Quit the app. Re-open it. Attempt to open a code module or a
form in design mode. That generates a MS generated "Gee, we are sorry
but we need to close this corrupted app." msgbox.

I think we are stuck with an inferior product, Phil.

On Nov 23, 2:11*pm, Patrick Finucane <patrickfinucan... (AT) gmail (DOT) com>
wrote:
My apps were crashing so many times I set up a desktop icon to run the
decompile. This afternoon an app crashed and the decompile would
fail. I was getting VB???.Tmp files generated in the folder. I read
something at the following link
http://answers.microsoft.com/en-us/o...1-f55d40af271b.
It said to run the Decompile at the DOS level. AHA!!! When I ran it
from DOS the issue cleared.

On 23/11/2011 20:48:20, Patrick Finucane wrote:
I believe there is a hotfix, but I can't find out what it is or where to get
it. I thought it was office-kb2596585-fullfile-x86-glb.exe, but it came up
with an error of something like "there is nothing to fix". I need the hotfix
for Windows 7 64 bit and Access (Office) 2010 SP1.

Have yet again removed SP1 and it is relatively stable, butI still have to
decompile frequently.

Phil

Do you have the x86 or x64 version of Office installed?

If it's the x64 version (which, btw, Microsoft suggests probably isn't
necessary!), you'd need Office2010-kb2596585-fullfile-x64-glb.exe

Both are available through http://support.microsoft.com/kb/2596585

"Phil" wrote in message news:jak20b$esu$1 (AT) speranza (DOT) aioe.org...
I believe there is a hotfix, but I can't find out what it is or where to get
it. I thought it was office-kb2596585-fullfile-x86-glb.exe, but it came up
with an error of something like "there is nothing to fix". I need the hotfix
for Windows 7 64 bit and Access (Office) 2010 SP1.

Have yet again removed SP1 and it is relatively stable, butI still have to
decompile frequently.

Phil

On 24/11/2011 15:16:33, "Douglas J Steele" wrote:

It's the 32 bit version of Office

Phil

As near as I can tell Access 2010 is extremely unstable. Decompile
sometimes works, sometimes doesn't. It constantly crashes when
opening anything dealing with VBA Perhaps it's MS's subtle way of
moving developers from VBA into macros.

Access 2010 is a pretty program. As one manager said to me many years
ago "I prefer an ugly program that works to a pretty program that
doesn't."

For those of you unfamiliar with the A2010 feature...one designs some
tables and forms with some code and some modules. Works like a
champ. Quit the app. Re-open it. Attempt to open a code module or a
form in design mode. That generates a MS generated "Gee, we are sorry
but we need to close this corrupted app." msgbox.

I think we are stuck with an inferior product, Phil.<<

FYI, I've been using 2010 for about 9 months as my primary version - both
with new accdbs, old mdbs, and mdbs that were converted to accdbs. I have
not had a corrupted database once. Not once. So perhaps it's something with
your install? Maybe uninstall and reinstall? For me, 2010 is working like a
charm, and I'm loving using it.

I will say, though, that it has a problem with 2007 databases. Once you
modify it in 2010, you can't use it again 2007, even if you don't apply any
of the 2010-only features. But that problem is common knowledge.

Anyway, I'm running XP and 32 bit Access 2010. FYI.

Neil

On Nov 30, 12:24*am, "Neil" <neil.ginsberg+newsgr... (AT) gmail (DOT) com> wrote:
Hi Neil. Knock on wood. It's an issue MS is aware of. I like A2010
tho I preferred the ribbon in A2007. I'm sure my issue of corruption
is due to some conflict with some hardware or software or security
feature which I have no control over at work. It's simply annoying to
work on a mdb, close it, reopen it, and have it corrupted.

What had me scratching my head was the running a Decompile from a
desktop icon and failing but following a MS's solution to run the
Decompile from DOS which works. I am unsure why the decompile works
from DOS but not from Windows.-

On 30/11/2011 15:11:22, Patrick Finucane wrote:
I use a little batch file

Copy "C:\Phil Data\Access\MDB 2010\Clubs 2012.accdb", "C:\Phil
Data\Access\MDB 2010\Decompile Clubs 2012.accdb"
"C:\Program Files (X86)\Microsoft Office\Office14\MSACCESS.EXE" "C:\Phil
Data\Access\MDB 2010\Decompile Clubs 2012.accdb" /decompile

This creates a new database "Decompile Clubs 2012.accdb"
I then rename the original database and include the date, and rename
Decompile Clubs 2012.accdbDecompile Clubs 2012.accdb back to the original
name of "Clubs 2012.accdb"

Spoke - yes actually spoke to a Microsoft professional about the problem, and
there is a hotfix

See http://support.microsoft.com/kb/2596585
Apparently if you are using 64 bit windows, the automatic fix thinks you will
be using 64 bit Office, and I guess most of us are using 32 bit Office

If you installed the x32-bit version of Office, select the “x86” Platform
version of the fix. (office2010kb2596585fullfilex86glb)

If you installed the x64-bit version of Office, select the “x64” Platform
version of the fix. (office2010kb2596585fullfilex64glb)

Seemed to work for me, but no guarantees

Phil

I can imagine!

Decompile from DOS which works. I am unsure why the decompile works
from DOS but not from Windows.<<

That is weird. I run Decompile from the pop-up menu (added it to the accdb
file type). Seems to work fine for me from there.



..