Unrecognized database

[Guest]

I have a FE and BE database on a server. Currently, users login from their
own PC's to the FE database that is on the server. The BE database has links
into tables of data that is stored in separate databases on the same server.
Over the last few weeks, we have seen an increase in the number of times the
"Unrecognized database" error messages popping up several times throughout
the day. I've been doing research and understand the latest version of jet
should be on all PC's that are accessing the FE on the server. All of the
PC's either have Access 2000 or Access 2002 installed. Some with Access 2000
still have an old service Pack (SR1). We are in the process of updating all
the PC's that haven't been updated recently with all the most recent updates.
It's very difficult to determine who or what is causing the corruption. Is
it possible that part of the corruption is on the server side where the
databases are located and that the combination of various versions of jets,
and service packs on a uses PC's in conjuction with what the server has is
causing the corruption? I have no details to provide about the server that
the db's are on. Are there certain questions I should ask?

 

[Ken Snell [MVP]]

Sharing a front end is an invitation to corruption...which is often the
cause of the error message that you're seeing. You should provide a copy of
the front end to each user on his/her own PC, and those front ends should
link to the backend file that contains the data.

See these articles for more info about splitting a database:

http://www.granite.ab.ca/access/splitapp/index.htm

http://www.allenbrowne.com/ser-01.html


You give each user his/her own copy of the front end file. The back end file
is put on a network server in a shared folder. All users must have
read/write/create/delete privileges on that shared folder. The front end
must be linked to the tables in the back end using the location of the back
end file. There is code available that enables your front end to
automatically restore links to the backend. See The ACCESS Web:
http://www.mvps.org/access/tables/tbl0009.htm

I personally use a function that I wrote that uses a table in the front end
(I store various paths to link to the back end in that table, each is
prioritized so that I can use the front end for development and for
distribution without having to keep changing paths in the table) to get the
path, and then to relink to the tables.

 

[Joseph Meehan]

I have a FE and BE database on a server. Currently, users login from
their own PC's to the FE database that is on the server.

Beep! Fe's belong on the individual's own PC. They don't share one,
they get their own.

The BE
database has links into tables of data that is stored in separate
databases on the same server.

While that may be OK, you make it sound like the BE is only a switching
station. Normally the FE should link directly to the database(s) that have
the data needed.

Over the last few weeks, we have seen
an increase in the number of times the "Unrecognized database" error
messages popping up several times throughout the day. I've been
doing research and understand the latest version of jet should be on
all PC's that are accessing the FE on the server.

Not just the latest version, all versions.

All of the PC's
either have Access 2000 or Access 2002 installed. Some with Access
2000 still have an old service Pack (SR1). We are in the process of
updating all the PC's that haven't been updated recently with all the
most recent updates. It's very difficult to determine who or what is
causing the corruption.

Not so hard. Just give each user their own FE.

 

[Guest]

Beep! Fe's belong on the individual's own PC. They don't share one,
they get their own.

 

[Guest]

I appreciate your input and will follow up on the information you provided.
I realized now that I failed to mention that the database is a secured
database. Would there be any other options available outside of splitting?

 

[Joseph Meehan]

No difference, but it is good to have it secured if you know how to do
it. It would be especially important for that many users.

I can almost guarantee you that with 40 users doing as you are doing you
are going to have continuous problems if you do not split it with the FE on
each user's machine.

I don't have the information, but there are several people here who can
help you set up a system to do updates to the FE's. If you do a search,
you should find your answer as there have been some recent questions on just
that.

I did not have the benefit of knowing about those systems so I just
added a little of my own code that would check version numbers. I had it
set to allow three cases. "OK", "Workable but should be updated", and I
can't allow you any more access without update."
For OK there was not message for the second there was a message and for the
last it gave a message and would go no further.

 

[Ken Snell [MVP]]

If you want to eliminate this source of corruption, splitting is your only
answer -- unless you limit the use of the database to a single person at any
time.

You can secure the backend database file.
--

Ken Snell
<MS ACCESS MVP>

 

[Guest]

Again, thanks for your input. It looks like I have my work cut out for me..

 

[Guest]

Thanks for the input. I best get started...

If you want to eliminate this source of corruption, splitting is your only
answer -- unless you limit the use of the database to a single person at any
time.

You can secure the backend database file.

 

[Tony Toews]

You've already received some excellent advice on giving each user
their own copy of the FE.

All of the
PC's either have Access 2000 or Access 2002 installed. Some with Access 2000
still have an old service Pack (SR1).

More important than being up to date with the Access SPs and SRs is
the Jet version. This should be the same on all the PCs.

What I've done is use the various API calls available and am checking
the version number and date/time of a crucial dll, msjetxx.dll, to
ensure it matches what I have on my system. See the Verify
Appropriate Jet Service Pack is installed page at my website for more
details including sample code:
www.granite.ab.ca\access\verifyjetsp.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