Multiple Database users

[Guest]

Hi All,

I’m relatively new to Access and I have developed a small database that
records the details of applications that we receive. The users enter this
information via a form.

Could someone please tell me how to set up the database so that I can have
multi users entering information at the same time? I’m sure it can be done
just don’t know where to start.

I am using Access 2003.

Thanks in advance.

 

[Guest]

I have never answered a question in the forum before so here goes.

See this excelent link by Albert Kalall
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

Mike

 

[John Vinson]

Hi All,

I’m relatively new to Access and I have developed a small database that
records the details of applications that we receive. The users enter this
information via a form.

Could someone please tell me how to set up the database so that I can have
multi users entering information at the same time? I’m sure it can be done
just don’t know where to start.

I am using Access 2003.

Thanks in advance.

Access, out of the box, with no modifications, allows (nominally) 255
concurrent users. In practice 30 or 40 is more reasonable. And in
reality, you really need to split the database; Mike posted the link
to Albert Kallal's page on splitting which should point you in the
right direction.

John W. Vinson[MVP]

 

[Tony Toews]

Could someone please tell me how to set up the database so that I can have
multi users entering information at the same time? I’m sure it can be done
just don’t know where to start.

You want to split the MDB into a front end containing the queries,
forms, reports, macros and modules with just the tables and
relationships. The FE is copied to each network users computer. The
FE MDB is linked to the tables in the back end MDB which resides on a
server. You make updates to the FE MDB and distribute them to the
users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp/ for more info. See the
Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. The utility also supports Terminal Server/Citrix quite
nicely.

The three most common performance problems in Access 2000 or newer
are:
- LDB locking which a persistent recordset connection or an always
open bound form corrects (multiple users)
- sub datasheet Name property set to [Auto] should be [None]
- Track name AutoCorrect should be off

If the problem is for everyone when starting up the MDB then it likely
needs a decompile.

For more information on these, less likely causes, other tips and
links to MS KB articles visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm