I have created a database which serves as an invoice
register to be used by two users and stored on our server
(G: drive). I have split the database and saved the BE and
FE in a folder of the G:. I then copied the FE and pasted

We have upgraded our Access 97 to Access 2003. After the
upgrade, the database always have locking problems and
the database cannot be repaired some of the data was
corrupted. Can someone help in the captioned problem?

We have a Novell based network with Win 2000 Servers connecting and
utilizing a BE database on a Novell volume.  No Problem.  Will an Access
97 FE (no hopes of upgrading at this time) run on 2003 server or will it
bomb?

I want to access a database under Oracle 9.x using Access
FrontEnd (mde). The problem is that a data record is not
locked when a user is working on this data record. This
means that several persons can work with the same data

When I try to convert my database (which has not been split) I am prompted
to select a new name.  Will all of my security information - users, groups,
rules, etc.  remain intact?  Are there any "gottcha's" that I should be
aware of?

This is such a basic question, but difficult to ask because of my ignorance.
But, here is the situation:
I have developed a split db.  The government agency I work for is asking
whether this db can be networked to potential users throughout the state.

I have a backend Access 97 database that which has tables
accessed from a front-end Access 97 application.  The
front-end application is essentially just a form which
queries the linked tables to the backend database.  This

Hi - I'm not a developer so please keep it simple!  But -
If I have an Access XP (2002) database and I want
to 'share' it with people on a network who only have
Access 97. Which is the best way to go about it?

I was wondering if anybody has any experience putting an
Access database on an SBS 2003 server and running it from
clients.  How does it behave?  Are the changes dynamic
among the clients and server or does everything have to be

We are currently using Access 2002 in a multi-user
environment. Every once in a while, one of the users will
receive and error message stating that currently the
database is locked by user such-n-such on machine such-n-

Does anyone know if oplocks is an issue with Access 97 and
Windows Server 2000 or 2003?  I seem to recall that we had
to turn off Oplocks for Windows NT Server by editing the
registry on only the server and not workstations.  Is my

I really need some help..Big time. I just installed access
2003 on networked computers. Using Server 2003 to hold the
mdb. I have 2 pc's logged onto the server. Seems the
application locks while doing a query. The shared data

USING WINDOWS XP HOME & OFFICE 2000 & SMALL NETWORK.  HOW
DO I SET WHERE ONLY ONE COMPUTER CAN OPEN DATABASE AT A
TIME??

I have a be mdb for Dev and Test and have located them on the server in a Development and Test folder, respectively.
The front end mdbs are located on my C: in their own Dev and Test folders.
The fe filenames (Metrics.mdb) are the same in Dev and Test C: drive folders, and the be ...

I created a small database that allows several of our users to update the
'notes' field for our records.  That is all they can do.
The database has only one form that opens and it only displays records for
the logged on user.  the form is based on a query being run with owner's