Need MVP - (Error Report)

[Jim]

I have a single file custom *.mdb database that was built
in Access 2000 (along with Access 2000 VBA - laboratory
application). We have several data entry persons and we
upgraded their machines to Access 2003 to improve their
data entry performance. The db has not been converted
to '03 because we have query users who are using Access
2000. All machines are Windows 2000.

At least once a day the data entry persons get an Error
Report dialog box with the check box "Repair my open
database and restart Microsoft Office Access" checked. To
fix this problem on the affected machine, I have them un-
select the check box, click the "Don't Send" button,
(already sent to MS the first time) do an ALT-F11 to get
into the code window, they select "Debug" then "Compile"
and they're on their way entering data. I never had this
problem with Access 2000.

Why do we have to constantly recompile, especially when
that has already been done (no code changes)? I need to
get rid of this Error Report situation. I have a copy of
the Error Report screenshots to send to someone, but I
need an email address.

Thank you!

 

[Kevin3NF]

Single file .mdb with several data-entry users? Have you looked at
splitting the DB? This may well fix the issue...

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.

 

[Jim]

Kevin,

Thanks for the reply. Here's the deal, I had no problems
with Access 2000, so why do I have problems now with
Access 2003? Also, up to this point I have not deemed it
necessary to split it for several reasons, one of which is
my knowledge about splitting (support and other
consequences) and I don't have much time to do the support
(the db is an add-on support job). My issue appears to be
with Access 2003 and some kind of backwards
incompatibility.

Jim

 

[Tony Toews]

I have a single file custom *.mdb database that was built

Kevin's right. The first thing to do is to split your MDB.

You want to split the MDB into a front end containing the queries,
forms, reports, macros and modules with just the tables and
relationships. The FE is copied to each network users computer. The
FE MDB is linked to the tables in the back end MDB which resides on a
server. You make updates to the FE MDB and distribute them to the
users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp/ for more info. See the
Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. It also supports Terminal Server/Citrix quite nicely.

For more information on corruption including possible causes,
determining the offending PC, retrieving your data, links, official MS
KB articles and a list of vendors who state they can fix corruption
see the Microsoft Access Corruption FAQ at
http://www.granite.ab.ca/access/corruptmdbs.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Kevin3NF]

Jim,

I'm not up to speed on Access 2003, but it is likely picking up "minor"
issues that Access 2000 was not.

Splitting the database is so simple there's a wizard for it. There should
be less support hassles after the split than before, especially if you
modify the non-table objects down the road.

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.

 

[Brendan Reynolds]

It's not necessarily an Access 2003-specific issue at all, Jim. We often see
posts from people who have been sharing a single MDB for some time with no
problems, and then suddenly start having problems, without having changed
the version of Access. The bottom line is that while you may be lucky and
get away with sharing a single MDB for years, it is a problem waiting to
happen.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.