I'm in the middle of building a database in access 2002 for a client
of mine. I just wanted to know what my choices were to make this
database accessable from multiple clients at once.

His network is a windows 2000 domain with about 8 workstations that
will use this database.

I read about an MDE file, but I when i tried to make it froze up my
system.

What are my choices?

ricky (AT) rickybell (DOT) com (InDeSkize) wrote in message news:<22935d4a.0405271156.75bbb5ca (AT) posting (DOT) google.com>...
Hello Ricky,

One of the ways that seems to be the best is to
set up two mdb files. 1. Front End (Loaded onto users
computers. 2. Back End (Loaded onto the network with
the Front End linked to it.) The Front End has the queries,
forms, reports, macros and modules. The Back End has the
tables only.

This way, if an update is needed for, say another report is
needed, only the front end has to be updated and copied over
the older version without any data loss.

One other thing, the Front End, after develeopent, can be
made into an MDE file so that the users can't edit it as
easily. Then distribute that onto the users computers.

Remember, ALWAYS keep a copy of your development MDB file
for future updates and then make a copy of it as an MDE file.

Regards,

Ray

Thanks for your help Ray.

I split the database with no problems. Everything seems to be running
fast. The problem that I'm still having, and I don't know if anyone
else has seen this before, is that when I click on Make MDE File,
access stops responding and nothing happens. One time I let it go
over night, nothing. Where I told it to put the MDE file comes up a
db1.mde file. I open it and after a series of "file not found"
messages I get my first switchboard with no buttons.

I've tried this on 3 different machines, 2 different versions of
Office (XP and 2003). So it's definately my database that doesn't
want to convert.

Anyone seen this before?