Input from multiple computers

[Guest]

Have had great help in designing my database here, and need a little more.

My database is designed and ready for input. There is a lot of data, and so
it will be split amongst 3 or 4 people on different computers so that they
can input simultaneously to speed things up.

Should I simply append their data to the "central" database file?

Any advice/suggestions/guidance in setting this up would be much appreciated.

 

[Arvin Meyer [MVP]]

Split the database into a front-end for all the forms, etc. linked to a
back-end with all the data tables. There is a database splitting wizard at:

Tools >>> Database Utilities >>> Database Splitter to help you.

Put both files on a server and relink the front to the back, then copy the
front-end to each users workstation.

That should do it.

 

[Guest]

Thank you. They will all input directly into the tables?

I will have to read up on this to understand it better, but is that the idea?

--
Thanks!

Dee

Split the database into a front-end for all the forms, etc. linked to a
back-end with all the data tables. There is a database splitting wizard at:

Tools >>> Database Utilities >>> Database Splitter to help you.

Put both files on a server and relink the front to the back, then copy the
front-end to each users workstation.

That should do it.

 

[John W. Vinson]

Thank you. They will all input directly into the tables?

I will have to read up on this to understand it better, but is that the idea?

See http://www.granite.ab.ca/access/splitapp.htm for a thorough discussion of
this kind of split application. All users will share the same tables (if it's
done correctly!)

John W. Vinson [MVP]

 

[Guest]

Thanks so much for the information and link. I will read it thoroughly and
make sure it's done properly!

--
Thanks!

Dee

 

[Guest]

One question. Can this be done without VBA code? (I hope)

--
Thanks!

Dee

 

[John W. Vinson]

One question. Can this be done without VBA code? (I hope)

Yes, though you may need to do a bit more manual work. Tools... Database
Utilities... Database Splitter Wizard will do the initial split, leaving you
with a frontend of the same name as your current database (MyData.mdb let's
say), and a backend named by adding _BE to the name; MyData_BE.mdb.

You would put the backend on a shared folder on the network, accessible to all
users (they'll need full Read, Write, Create and Delete privileges to the
folder). Each user will get a copy of MyData.mdb.

If not everyone uses the same drive name mapping - e.g. if you have the shared
backend folder as your E: drive and Fred down the hall has it as K: - you'll
need to open each frontend, once it's on the user's computer, and use Tools...
Database Utilities... Linked Table Manager to relink to that user's version of
the backend location.

John W. Vinson [MVP]

 

[Guest]

Thank you so much for these clear details. You really explain things well!

Will do my reading up on it and then put it into practice next week.

Thanks again! (as always)
--
Thanks!

Dee

 

[Arvin Meyer [MVP]]

Thank you. They will all input directly into the tables?

No, you don't want that. Access/Jet is not a server based engine so there's
no way to enforce certain rules that are easy to do with code. While it
isn't necessary to enforce rules, especially with a well trained staff doing
data input, it's a good idea to make it possible. So event if you want to
use direct input into tables, I'd suggest using a datasheet view of a form
instead. That will allow you to grow smoothly should you desire to do so.

 

[Guest]

If I understand your reply, I think you (for a good reason) misunderstood my
post. I meant they will input directly into the tables, but via forms.

I have a number of forms (mostly with subforms) that they will use. Is that
correct?

--
Thanks!

Dee

 

[Arvin Meyer [MVP]]

If I understand your reply, I think you (for a good reason) misunderstood
my
post. I meant they will input directly into the tables, but via forms.

I have a number of forms (mostly with subforms) that they will use. Is
that
correct?

Perfect!