This may sound like a dumb question coming up but please bear with me.
I've been experimenting with automating the updates of front-ends.
Starting to write a batch file etc. when the following just occurred
to me.

I am in the middle of developing a stand-alone database application for one
of my clients using Microsoft Access 2000.
My client does not have any of the Access versions.
I would like to know the current state of affairs with regard to Microsoft

Are there any problems putting an Access XP backend
database on a compressed drive? e.g. performance,
corruption.
Thanks.

I've made some small applications in Access before to be used by several
people at work.
Now as things move on I have about 5 apllics that run , doing most of the
time the same things but with different data.

  I have done a couple of posts before but am VERY nervous about deploying
a small app that I have developed for my department. The issues are
1) I have created a master database and a client which has linked tables to
the master. Firstly is this the right way to do this?

I'm looking to deploy an Access application across a large number of
users and would like input from those of you out there who have had
real-life experience with a deployment of this size.  Here's the
details:

I'm pretty novice on multiuser issues
I have a backend .mdb file on the server, but I also have the frontend .mdb
file on the server. All my useres (8 - 10) access the same front end .mdb
file. Would it be more efficient to copy a the FE file down to the local

Hy,
A problem from a non-experimented programmer in a multi
user environment:
I have a database “MasterAchat” which contains a linked

Further to this, the server this isn't working with is a
Windows 2000 server.  Our previous server, which was
Windows NT, is fine.

Could anyone tell me what the maximum number of clients
Access XP can handle and where on the microsoft website
it gives me those specifications.
Thanks,

I am developing a multi-user secured database in Access 2000.
The database is split backend on server, frontend on local machine.
There are two mdw files in use: develop.mdw and users.mdw
both are stored on the server in the same directory as the backend.

I have a split database, with the backend (Access97 ver.) stored on a
Windows XP machine and appropriate versions of the frontend on a Windows 98
machine and on the XP machine.
If I open the Windows XP frontend (Access2000 ver.) first, then I can

I think I know what the answer to this question will be ("No you
can't), but I'm hoping I'm wrong.
At a given workstation, can you prevent the user from loading multiple
instances of the  Access app.?

hi im setting up a muti user database in one of my tables ive got
inputby
inputbydts
remarkedby

I'm doing a project at work which requires job-sheets to be printed to
department printers.
How do I use access to automatically change to the printer associated to the
department?