Access 2K and a consistant Database Repairing

[Brian]

I have a small application with 2 forms where the user logs into the system,
then the form recordsource randomly pulls up an account ID. The application
is basically an electronic tic sheet and reporting tool. Once the user is
done they select a check box then system appends the record into a completed
record table. There are about 25 users. I have the database split into a
frontend MDE file and the backend is a mdb file.

The users can log in and work in the system just fine, but after a couple of
hours if a user exits the system or someone needs to sign on, a error
message comes saying the file is not a database or the file needs to be
repaired. Once you repair the system, all users can get back in and again
after a couple of hours it will need to be repair again. I also get the
problem if I use a MDB front end.

HELP !!!!!!!! Can ayone point to anything can help eliminate this issue.

Brian

[Thilo Immel]

Brian,

I have a small application with 2 forms where the user logs into the system,
then the form recordsource randomly pulls up an account ID. The application
is basically an electronic tic sheet and reporting tool. Once the user is
done they select a check box then system appends the record into a completed
record table. There are about 25 users. I have the database split into a
frontend MDE file and the backend is a mdb file.

The users can log in and work in the system just fine, but after a couple of
hours if a user exits the system or someone needs to sign on, a error
message comes saying the file is not a database or the file needs to be
repaired. Once you repair the system, all users can get back in and again
after a couple of hours it will need to be repair again. I also get the
problem if I use a MDB front end.

HELP !!!!!!!! Can ayone point to anything can help eliminate this issue.

You may have a look at Tony Toews Access Corruption FAQ site
http://www.granite.ab.ca/access/corruptmdbs.htm

We have a self help section at our site too
www.atroplan.com/infoe.htm

If you have an Win2000 or WinNt4.0 Server, you should disable
opportunistic locking.
Regards

Thilo Immel
The Access Druid www.atroplan.com

[Tony Toews]

ja******@bellsouth.net (Brian) wrote:

The users can log in and work in the system just fine, but after a couple of
hours if a user exits the system or someone needs to sign on, a error
message comes saying the file is not a database or the file needs to be
repaired. Once you repair the system, all users can get back in and again
after a couple of hours it will need to be repair again.

As Thilo mentions first thing I'd do is check out the OpLocks setting.

But which MDB is getting corrupted? The FE MDE or the BE MDB? You also imply that
your users are sharing the FE MDE. Or at least you haven't stated that each user
gets thier own copy.

You really want to put the FE on each machine or place in a user specific directory
on the server. This will help avoid some weird error messages when users are
changing the same forms record source, filters and such as well as corruptions.

I specifically created the Auto FE Updater utility so that I could make changes to
the FE MDE as often as I wanted and be quite confident that the next time someone
went to run the app that it would pull in the latest version. For more info on the
errors or the Auto FE Updater utility see the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the FE on each PC up
to date.

In a Terminal Server or Citrix environment the Auto FE Updater now supports creating
a directory named after the user on a server. Given a choice put the FE on the
Citrix server to reduce network traffic and to avoid having to load objects over the
network which can be somewhat sluggish.

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

[Brian]

I beleve the errors are coming in on the FE, but I will obviously have to do
some more research.
The FE is in a specified directory on the server. I was looking around and
saw your app. This will make
giving each user their own app much easier. With so many to deal with, I
hadn't planned doing it.

I read the items on the OpLock so I will have to check that in the morning.

thanks, Brian

"Tony Toews" <tt****@telusplanet.net> wrote in message
news:pm********************************@4ax.com...

ja******@bellsouth.net (Brian) wrote:

The users can log in and work in the system just fine, but after a couple
of
hours if a user exits the system or someone needs to sign on, a error
message comes saying the file is not a database or the file needs to be
repaired. Once you repair the system, all users can get back in and again
after a couple of hours it will need to be repair again.

As Thilo mentions first thing I'd do is check out the OpLocks setting.

But which MDB is getting corrupted? The FE MDE or the BE MDB? You also
imply that
your users are sharing the FE MDE. Or at least you haven't stated that
each user
gets thier own copy.

You really want to put the FE on each machine or place in a user specific
directory
on the server. This will help avoid some weird error messages when users
are
changing the same forms record source, filters and such as well as
corruptions.

I specifically created the Auto FE Updater utility so that I could make
changes to
the FE MDE as often as I wanted and be quite confident that the next time
someone
went to run the app that it would pull in the latest version. For more
info on the
errors or the Auto FE Updater utility see the free Auto FE Updater utility
at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the FE on
each PC up
to date.

In a Terminal Server or Citrix environment the Auto FE Updater now
supports creating
a directory named after the user on a server. Given a choice put the FE
on the
Citrix server to reduce network traffic and to avoid having to load
objects over the
network which can be somewhat sluggish.

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

[Brian]

OK, I have another question, I know out workstations are using sp4, and I'm
pretty sure the servers are using sp4, in article 300216 it states that sp3
must be installed on both the server and workstation. If sp4 is in both
location, do I still need to see about having the OpLock disabled?
I don't have direct access to these machines, so it might take an act of god
to mess with the registry.

Brian
"Tony Toews" <tt****@telusplanet.net> wrote in message
news:pm********************************@4ax.com...

ja******@bellsouth.net (Brian) wrote:

The users can log in and work in the system just fine, but after a couple
of
hours if a user exits the system or someone needs to sign on, a error
message comes saying the file is not a database or the file needs to be
repaired. Once you repair the system, all users can get back in and again
after a couple of hours it will need to be repair again.

As Thilo mentions first thing I'd do is check out the OpLocks setting.

But which MDB is getting corrupted? The FE MDE or the BE MDB? You also
imply that
your users are sharing the FE MDE. Or at least you haven't stated that
each user
gets thier own copy.

You really want to put the FE on each machine or place in a user specific
directory
on the server. This will help avoid some weird error messages when users
are
changing the same forms record source, filters and such as well as
corruptions.

I specifically created the Auto FE Updater utility so that I could make
changes to
the FE MDE as often as I wanted and be quite confident that the next time
someone
went to run the app that it would pull in the latest version. For more
info on the
errors or the Auto FE Updater utility see the free Auto FE Updater utility
at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the FE on
each PC up
to date.

In a Terminal Server or Citrix environment the Auto FE Updater now
supports creating
a directory named after the user on a server. Given a choice put the FE
on the
Citrix server to reduce network traffic and to avoid having to load
objects over the
network which can be somewhat sluggish.

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

[Tony Toews]

"Brian" <ja******@bellsouth.net> wrote:

OK, I have another question, I know out workstations are using sp4, and I'm
pretty sure the servers are using sp4, in article 300216 it states that sp3
must be installed on both the server and workstation. If sp4 is in both
location, do I still need to see about having the OpLock disabled?
Supposedly not. But I have to admit I'm not entirely convinced.
I don't have direct access to these machines, so it might take an act of god
to mess with the registry.

All you need to update is the registry on the server. And reboot it. But I hear you
that this could take a lot of work convincing IT Nazis.

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