Access 2003 APPCRASH on 64 bit

[NeoK]

Dear all,

since a couple of days I'm having a big problem with Access 2003 on both
Windows 2008 Server and Windows 7 RC, both 64 bit. On both systems Access
crashes with an APPCRASH whenever trying to either compact and repair and/or
- and this is really a problem! - create an .ade file (based in the adb I
use). To be clear: I'm not complaining about the RC, but about the W2K 2008,
which should be stable!

All of this works perfectly fine on my netbook with Windows XP Home. So yes,
I have a workaround, but it's really a pain, as I have to copy the .adb-file
from my development pc (Windows 7) to my netbook, make the ade there, then
copy it back again, transfer it to the server, change the connection to
SQL-server (from development server to production).... instead of doing this
all directly on the server via TS!

Anything that I missed, like Access 2003 with SP3 doesn't work on 64 bit!?

(Beside that, sadly I have to say: If I had know that Access was simply
"dropped" by MS, I hadn't developed my last application still with the "easy
way" Access, but switched to ANYTHING else. The problems I had to find
workarounds using adp have been really frustrating...!)

Thanks for any help!
Klaus

 

[Larry Linson]

(Beside that, sadly I have to say: If I had know that Access
was simply "dropped" by MS,

Why would you jump to that conclusion? It seems to me that "compatibility
issue" with 32-bit Office and 64-bit Operating System would be a more
logical guess.

I'm not using, and thus have not investigated, Microsoft's statements on
compatibility between its 64-bit OSs and 32-bit applications. Has M'soft
committed to supporting 32-bit Office on those OSes? If so, you should be
reporting a bug to M'soft instead of asking in an Access newsgroup.

I hadn't developed my last application still with the
"easy way" Access, but switched to ANYTHING else.
The problems I had to find workarounds using adp
have been really frustrating...!)

It would be just a little amazing to me, if the developers of Office/Access
2003 had been privy to all the details of then-undeveloped, and
not-fully-designed Operating Systems. Don't you agree? So, it would be
incumbent on the developers of the OS to determine with which previous
versions they would be compatible, implement, and test in that way.

Because we keep hearing that "the world is moving to 64-bit" and because
Microsoft has stated that Access is NOT "going away", it seems reasonable to
assume that there will be either accomodation to support 32-bit versions of
Office or to release a 64-bit version of Office.

Larry Linson
Microsoft Office Access MVP

 

[david]

But, of course, no reason to expect a 64 bit version of ADP,
or a fix for 32 bit ADP's on W64, since MS doesn't do fixes
to backward-compatibility applications when there is a work-around.

(david)

 

[NeoK]

@David: Well, the "workaround" is to not use a 64bit-OS.... which is a bit of
a problem if my TS is 64bit, and I don't want to switch back to 32bit "only"
because of Access... (I could also switch back to Access 2.0 and Win98 with
similar arguments...)

@Larry: My frustrated and surly emotional remark was related to problems I
had in the past, and so (long) before switching to 64 bit! But it should not
be part of this thread to talk about all this old issues here...

btw, it worked for a couple of weeks, but now it doesn't anymore. So of
course at first I thought about a problem of the adp, but as it's no problem
to create an ade on WinXP 32bit, and both W2K8 and W7 are 64bit, I assume
the problem is the combination 32bit Access with 64bit OS + maybe an update
that was rolled out by MS recently.... I will have to check this.

Of course you're right, I assume MS never committed 32bit apps to run on
64bit OS. So how could a customer simply expect it to work... sorry for
sarcasm, but let me ask you the question in return: Why should a customer NOT
expect it to work?

You can be sure that I tried it, BEFORE switching to 64bit! Having problems
like that, now, after weeks without problems, is of course frustrating (esp.
as there only seem to be about 4 persons around the world having the same
problems so far, assuming to my internet search result).

But well, maybe there is a solution by deinstalling (if possible) one of the
last updates...

Regards,
Klaus