access database for multiple users

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

hi.
if i create a database using access 2000 and put it on a network, will multiple users be able to access it at the same time. the database will be creating invoices so more than one users will be working at a time. only one users will be working with one customer at a time.
thanks.
 
You certainly can! Generally, the steps are as follows:

1. If you have not already done so, split the application into a Front-End
and a Back-End. The Front-End (FE) will contain all Queries, Forms,
Reports, Modules, Macros and local-use tables. The Back-End (BE) will
contain all tables to be shared among users.

2. The BE will reside in a folder on your server, where full permissions
for each user will be granted (Read, Write, Create, Delete, Execute).

3. In the FE, Link to the tables in the BE. To avoid problems with
changing drive mappings, link to the BE tables using the full UNC, starting
with My Network Places and drilling down through folders until the actual
database name of the BE is found.

4. An individual copy of each FE will reside on each user's computer. For
ease of distributing updates to FEs, see:
http://www.granite.ab.ca/access/autofe.htm which describes an AutoUpdater
for front-ends, developed by Access MVP Tony Toews.

5. Additionally, a copy of the most current FE in use by users should be
kept on the server. You will do your maintenance/update programming on your
own copy of the FE on your own computer. When updates are ready to be
distributed, you'll copy your modified FE to replace the one on the server.

Those are pretty much the high points. Post back if you need more.



--
Cheryl Fischer
Law/Sys Associates
Houston, TX

megan said:
hi.
if i create a database using access 2000 and put it on a network, will
Click to expand...
multiple users be able to access it at the same time. the database will be
creating invoices so more than one users will be working at a time. only one
users will be working with one customer at a time.
 
thanks.
actually, i hadn't split it. i'm not even sure the network computer is a "server". it's more like a centeralized computer. i'll look at your link. this is all pretty new to me. i'm still actually learnng access. i've done other coding but it's been a while.
will appreciate any advise or informational links.
 
For this conversation, server can mean any machine the users can get to from
their workstations. A strong PC is sufficient for a number of my customers.
Just make sure to include a backup plan in your process.

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm

megan said:
thanks.
actually, i hadn't split it. i'm not even sure the network computer is a
Click to expand...
"server". it's more like a centeralized computer. i'll look at your link.
this is all pretty new to me. i'm still actually learnng access. i've done
other coding but it's been a while.
 
thanks for the help.
i don't mean to be stupid - but by creating a front end and a back end - am I really creating 2 mdb files and then linking them?
i'm going to need to stack my queries -
for example, a query that will find if a customer is on a price tier or specialized pricing - if a tier - go there if specialized use the product and customer id to get their pricing. may be too choppy. still in design but this is what my friends are asking for.
i apologize for my lack of finesse but i have a short time frame and have bitten off too much i think.
thanks again.
 
Yes, you will be creating two mdbs and linking them.

How about a field in the customer table identifying whether they are tiered
or specialized, then perform your actions based on the contents of that
field?

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm

megan said:
thanks for the help.
i don't mean to be stupid - but by creating a front end and a back end -
Click to expand...
am I really creating 2 mdb files and then linking them?
i'm going to need to stack my queries -
for example, a query that will find if a customer is on a price tier or
Click to expand...
specialized pricing - if a tier - go there if specialized use the product
and customer id to get their pricing. may be too choppy. still in design but
this is what my friends are asking for.
 
Hi.
been self-teaching myself some 'advanced', well maybe not tha
advanced, Access with a couple of production db's and was curious abou
this 'splitting' idea. It sounds like a great idea, especially if a d
will need ongoing tweaks to forms, new reports, etc.

I would just like to ask for a bit more clarification on how that'
done please. If I understand it correctly, the db is actually
separate and distinct db's, one containing the tables, and on
containing everything else? The one containing the frms, qrys, rpts
etc then has to 'link' to the tables in the other db?
This doesn't cause any problems? To make modifications to the on
containing the objs, the users don't have to be out of them?

And if i may, how does a beginner start from scratch to learn th
custom programming behind access (VBA?) to get really creative whe
necessary?

thank you in advance for any input,
new to this site/foru

Lin
 
Ling said:
Hi.
been self-teaching myself some 'advanced', well maybe not that
advanced, Access with a couple of production db's and was curious about
this 'splitting' idea. It sounds like a great idea, especially if a db
will need ongoing tweaks to forms, new reports, etc.

I would just like to ask for a bit more clarification on how that's
done please. If I understand it correctly, the db is actually 2
separate and distinct db's, one containing the tables, and one
containing everything else? The one containing the frms, qrys, rpts,
etc then has to 'link' to the tables in the other db?
This doesn't cause any problems? To make modifications to the one
containing the objs, the users don't have to be out of them?
Click to expand...

When you split an app you can then have as many "front end" files as you
like. This allows you to gain extra advantages by giving each user their
own local copy of the front end instead of having them all share a common
one (highly recommended).

This also means that you can be working on your own separate copy so there
is never a problem with others being in the file when you need to work on
it. When you are ready to send out your changes you just provide a means
for all of your users to replace their existing front end file with the new
one. It is this last step that can a lot of variation.

Depending on how often you issue updates and how many users you have you
might handle all of it with Emails or you might utilize a completely
automated process.
 
Back
Top