Multiple Machines

[Rob]

Hi,
XP Home and XP PRO
Access '03 & Access '07 (not necessary to use '07)

Can I access the same file on more than one machine?

I have a simple database with one table (so far) that my assistant and I
need to use. I am OK if it is not the same time.

Thanks

Rob

 

[Douglas J. Steele]

Yes, Access is multi-user right out of the box.

Note that the normal advice is split the database into a front-end
(containing the queries, forms, reports, macros and modules) and a back-end
(containing the tables and relationships). Only the back-end should be
shared: each user should have his/her own copy of the front-end, preferably
on his/her hard drive.

 

[Guest]

If the computers are not on a network, you can however you will need to use
replication which you will soon find is a PITA for your needs. You'll still
have to connect the two machines together at least once a month or so.

Your best bet is to have both computers on a network, even peer-to-peer, and
put the database file on a shared drive. Both of you could use the database
at once then. If only two users, you probably don't need to split the
database.

If both of you don't need to use the database at the same time, you could
buy a good sized flash drive and keep the database on it. Do frequent backups
as flash drives can get lost or stepped upon.

 

[Joseph Meehan]

Hi,
XP Home and XP PRO
Access '03 & Access '07 (not necessary to use '07)

Can I access the same file on more than one machine?

I have a simple database with one table (so far) that my assistant
and I need to use. I am OK if it is not the same time.

Thanks

Rob

Do you mean the same database file (data and definitions *.mdb or *.mde)
or program file (The Microsoft Access program)?

 

[Rob]

Sorry for being so impatient. I downloaded more headers and read through.

I have read that access is multi user out of the box. There was talk about
front end and back end, which makes sense to me.

Is this for servers only?

I have three machines and no server. We are connected and share folders.

Thanks

 

[Douglas J. Steele]

You can put the back-end database in a shared folder on one of the machines,
rather than use a server.

 

[Rob]

First I want to say thanks a whole lot I really appreciate the help and the
professionalism I receive here.


We are peer to peer and I do have a separate hard drive on my XP pro machine
for sharing. So I am understanding that I should put the main data base file
on my "G" drive (shared and XP Pro and a back up system) and then each user
creates a new db file and then chooses to open the file on my "G" drive. Is
that correct?

(I believe that *.mdb = Microsoft Data Base I am not sure what *.mde is)

I am at home this morning. I have two machines that are networked both XP
home and no separate HD to share. I created a simple database with one table
and one query, report and one form. I chose to split it and I now have a
file named pqsample_be

So am I to assume that I can go to my other machine and create a data base
and open the pqsample_be file and create my own queries and forms. Is there
any set up I need to do on the second machine?

 

[Arvin Meyer [MVP]]

Split the database as per Doug's suggestion. Put the tables database on the
computer that gets the least use and/or is the most powerful. Have all 3
computers link to it.

 

[Rob]

When you say link to it. Do you mean when I am in access on a different
machine. File> Get External Data> Link Tables?

 

[Douglas J. Steele]

Since you're strictly going to be copying the front end to each machine,
when you set the front end up in the first place, link using a UNC
(\\machine\share\folder\file.mdb), rather than using a drive letter
(G:\folder\file.mdb). To ensure this happens, when you use File |
GetExternalData | Link Tables, find the file through the Network
Neighborhood (or My Network Places, or whatever it's called).

If you didn't set it up that way, then you can always use the Linked Table
Manager on the subsequent machines to relink them correctly.

--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)

 

[Douglas J. Steele]

An MDE file compiles all modules, removes all editable source code, and
compacts the destination database. Your Visual Basic code will continue to
run, but it cannot be viewed or edited, and the size of your database will
be reduced due to the removal of the code. Additionally, memory usage is
optimized, which will improve performance. Since it cannot be changed, it's
important you keep a copy of the MDB file that was used to create the MDE
file!

When you split, presumably you also ended up with something like
pqsample.mdb that contains your query, report and form. Put that on the
other machine, and see if it works. If not, see what I posted elsewhere in
this thread about how you link front ends to back ends.

Yes, if so desired people can make their own forms, queries, reports, etc in
their front end. In general, though, most people like keeping the front ends
in synch.