Access 07 Crashes

[B_A_R_T_M_A_N]

Hello,

We have an Access 03 app that we are testing in Access 07. We have
discovered that in all datasheets if you right click on a field in a
column that doesn't have focus, Access shutsdown/crashes. If you left
click first on any field, then right click on that data field, no
problem. We have done this on three different PCs. Has anyone else
encountered this?

Things we have tried:
1. Convert to 07.
2. Run as 03 in 07.
3. Built new 07 and imported all forms, tables, macros, etc.

If we turn off the shortcut key on the forms, then no problems.

Any help would be greatly appreciated.

Bart

 

[Allen Browne]

Bart, I can't reproduce that. In Accesss 2007, I am able to right-click any
field in a datasheet (query or form in datasheet view) in an MDB created in
a previous version, without experiencing the crash.

See if a decompile fixes the problem. Whenever you switch Access versions,
there is a significant problem with the incompatible binaries between
versions. Just this week I had an A2000 MDE that instantly crashed any A2003
machine just on opening the database (so running startup code.)

Name AutoCorrect is always a suspect too, so try this sequence:

1. Uncheck the boxes under:
Office Button | Access Options | Current Database | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Office Button | Manage | Compact/Repair

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office12\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access (holding down the Shift key if you have any startup code),
and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, reference ambiguities are resolved,
and the code syntax is compilable.

 

[Guest]

We have uncovered a similar situation with Access 2007 and Windows Vista. If
you right click anywhere on a subform where there is no control, Access will
crash every time. However it works just fine on Windows XP and Windows 2003
SBS. It appears there is some sort of bug in the interface to Vista that is
causing the issue. Rather awkward with the user interface (AccessUI) that we
are using.

WendellB

 

[Aaron Kempf]

I'd reccomend using Access Data Projects

u don't want to play russian roulette with your DATA

 

[Guest]

The data is already in SQL Server, so using an ADP wouldn't help here. It
just that each time Access crashes, it wants to save a backup of the
front-end file. We've also discovered that the double-click function fails
to work, but it doesn't crash Access - it just doesn't do anything. Also
note that everything works just fine when running on XP or on Windows 2003.
There appears to be a bug in the event processing in Access 2007 when you
couple it with Windows Vista.

 

[Aaron Kempf]

if the data is in SQL Server and you're using MDB???

then you're helpless

ADP is 100 times easier than MDB

 

[Guest]

I must respectfully disagree with you. We've been doing MDB databases
connected to SQL Server backends since 1994, and have literally several
hundreds clients working in that mode without a problem. ADPs have a number
of limitations, such as no security model other than that provided by SQL
Server, and it's major pain to develop a form with nested subforms in an ADP.
ADPs do have their place - but the Access Development team has apparently
decided not to add any further enhancements to ADPs - so it's not clear to me
that ADPs are a logical choice.

The real issue here is that Access 2003 behaves properly whether running on
Vista or XP, and Access 2007 does not. Debating the merits of MDB versus ADP
is pointless.

 

[Guest]

It appears that Microsoft released a hotfix that is at least in a related
area for the problem you found. See MSKB 935875 for the details. Briefly,
it deals with the wrong right-click menu being displayed when working with an
Access 2003 MDB file running on Access 2007. Also, further testing has
determined that double-click events on a subform are not being processed when
running on a Vista system, but work just fine on a WinXP/2003 system.

 

[Aaron Kempf]

I militantly disagree

you lie and you are a con artist

I'm sorry.. you're saying that you PREFER user-level security to SQL Server
security??

ROFL ROFL ROFL ROFL ROFL

oh jeez-- I almost pee'd my pants when I read that

And where did you read 'the Access Development team has apparently decided
not to add any further enhancements to ADP'

serious bitch
where did you read that?

BECAUSE ACCORDING TO MY CALCULATIONS?
ADP HAS GOTTEN FIXES EVERY VERSION FOR THE PAST FOUR VERSIONS AND MDB DOES
NOT HAVE A SINGLE NEW PIECE OF FUNCTIONALITY

Serious kid
STFU until you know what you're talking about


SERIOUS
it is an ADP problem

you're a dipstick for usign MDB
anyone using MDB for anything.. should be FIRED and then SPIT UPON

 

[Aaron Kempf]

when MDB has a profiler, Analysis Services and DTS / SSIS built in-- that is
when MDB becomes relevent

until then you can take your FUD and shove it

JET and DAO haven't been included with Office, Windows or MDAC for a decade

stop smoking crack dork

 

[Aaron Kempf]

oh I disagree

I've been having 2700 users simulatenously update information in a
spreadsheet

GAG GAG GAG

 

[Aaron Kempf]

if the SQL Server Security Model is 'too difficult for the widdle baby
programmer' you know that you can BUY A BOOK RIGHT?

MDB is for lamers and retards
SERIOUSLY
stop spreading lies in MY FORUM