Upgraded Access Crashes

[John Smith]

Hi, we recently upgraded a suite of access databases from 97 to 2003 using
the auto upgrade feature in office 2003.

Since then we have been plagued by sporadic crashes. There appears to be no
pattern (Its not one specific set of records, or forms for example.)

Ive checked other online sites such as allenbrowne.com, and I have looked at
the forms where we have seen a crash, and there are no missing references,
and auto correct is off.

Can anyone else suggest what I should look at?

There are 3 databases, 2 which just contain tables, and a third that links
to the tables in the other 2, which contains all the forms and reports. The
databases are stored in different drives on the same server, and it doesnt
seem to matter whether the system is accessed from a specific machine.

Can anyone suggest what else I can try, as Im running out of ideas!

Cheers

 

[Jeff Boyce]

John

Are you saying you have a single copy of the front-end, located on a server?
If so, and if you have more than one user trying to run it simultaneously,
you could get corruption or other issues.

The standard recommendation (tablesdbdesign newsgroup) is to split your
database into a front-end and back-end, and put a copy of the front-end on
EVERY user's PC.

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[John Smith]

Thanks Jeff, I'll change the way we are set up.

But it doesn't explain the sporadic changes if the database is accessed from
the server.

Any more ideas?

 

[Jeff Boyce]

John

If you have multiple users hitting a single front-end on a server, I suppose
the other duties that server is doing could impact if/how Access runs.

Also, if any of your users have a flaky NIC or Ethernet cable or router, and
they are part of the group trying to use, you could get intermittent issues.

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[John Smith]

Thanks Jeff.


I don't believe that there are any hardware issues, but I'll get someone who
knows more about the wires to check.

To add one more piece of information into the pot, last time it crashed, I
managed to get one of the users to send me a screen shot, rather than just
say the stupid database has crashed again.

The Error Signature (and Im about to Google this as well) is;
ApName MSAccess.exe ApVer 11.0.6566.0 ApStamp 42cdb33e
ModName unknown ModVer 0.0.0.0 ModStamp 00000000
fDebug 0 Offset 0025a961

Does that mean anything to you?

Cheers

 

[Jeff Boyce]

John

Wish it did! Perhaps one of the other 'group readers has run across this
before.

Good luck in your search.

Have you considered adding an ErrorLog table and modifying your error
handling routine to write to the log? You'd get more accurate feedback
about what isn't working...

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[John Smith]

Thats the next Thing to try I guess.

My big issue is Ive never really worked on the system, (or with access that
much), Im left supporting it by default as I know about computers..

So I assume I'll need to look in each function and add an error handler if
one is no present, or is there some kind of default error handler I can use?

 

[Jeff Boyce]

John

Consider using a search tool (e.g., Google.com) to find references to error
handler routines folks have come up with.

Yes, each procedure would need to include an error handler, which would
basically simply point to the above routine. Even if a procedure has an
error handler, consider re-pointing to the common one mentioned above.

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[John Smith]

HI Jeff, Ive been to the office today and spent a while there.

It actually looks now like an issue with Service Packs.

(I copied the current software to my laptop and it ran without crashing.
Only difference is my laptop has never had service packs 1 and 2 applied to
office, whereas the machines with the problem do have.)

Just to be sure, I created new databases, turned the auto names boxes off,
adn then imported / linked to the other tables and forms, and the system
still crashed. (Which, according to what Ive read, tends to rule out a
courruption in the database.)

So thanks for your help, its over to the IT admin to see if he can provide a
machine in that department without SP 1 and 2, or apply any new hotfixes to
office, so we can investigate further.

Cheers, and have a good weekend.

 

[aaron.kempf]

I reccomend sending it to a professional development company and
upgrade to Access Data Projects.

MDB isn't ready for primetime; and it never has been


-Aaron