MULTI-USER Adding Record

[Fabio]

Hi,
I'm new to Access and a bit confused abt using it in a Multi-user environment.
Is it possible to have a single database with different users simultaneously
adding records and attachment (e.g. an Excel file) to it ? Is Access going to
work well with this ?

Thx vey much

 

[Tom Wickerath]

Hi Fabio,

Yes, it's certainly possible to have a multi-user Access application. It is
very important that you split your database into two .mdb files, commonly
known as a front-end (FE) and back-end (BE) files. Each user gets their own
copy of the FE application installed onto their local hard drive. Please see
my multi-user applications paper, available here:

http://www.accessmvp.com/TWickerath/

Are you wanting to link to an Excel file? I do not recommend attempting to
use OLE Embedding to embed files of any type in Access.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Fabio]

Thx Tom..

So it works perfectly fine when several users are simultaneously adding new
records to the "Back-End" file, as long as they're not editing the same
record. Am I right ?



"Tom Wickerath" 來函：

 

[Tom Wickerath]

Hi Fabio,

With a properly designed database, on a good solid local area network (LAN),
your statement is correct. Don't try to use Access on a WAN, unless you are
prepared to implement terminal services. Access MVP Albert Kallal has more to
say about this topic, here:

Using a wan with ms-access? How fast, how far?
http://www.members.shaw.ca/AlbertKallal/Wan/Wans.html


Make sure that all workstations are properly updated. See the bottom of page
1 (Best Practices) of my Word document named "Access Links.doc". You can
download a copy, here:

http://www.accessmvp.com/TWickerath/


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Fabio]

wow ...thx for your quick help on this ..Tom

"Tom Wickerath" 來函：

 

[Tom Wickerath]

You're welcome. While it is quite easy to create a single-user Access
application, there are many "gotchas" just waiting to bite you when you
attempt to allow multiple users to start using it. Therefore, I recommend
designing with a network in
mind. This includes minimizing the amount of data that must be brought over
the network wire, since a network represents the weak link in the chain.

With proper design, you should be able to create a solid multiuser Access
application that can easily support 40 to 50 simultaneous users. The golden
rule is to fetch only the data that a user needs. I have a new tutorial paper
available on the Seattle Access User Group, for a presentation that I gave a
few weeks ago. See the download, available here:

http://www.seattleaccess.org/downloads.htm

Query By Form - Multi Select
Tom Wickerath, February 12, 2008

Download (269kb) Using Multi-Select Options; Word doc and mdb


I will eventually convert this to a web page on my new web site, as time
permits. Make sure to follow all of the recommendations in my Multi-User
Applications write-up. This is a compilation of many years of learning the
hard way. For example, disable Name Autocorrect, set all table subdatasheets
to [None] (you must disable Name Autocorrect first, to get the table
subdatasheets setting to "stick"), establish a persistent connection, use
proper indexes, and use the JETShowPlan registry setting to ensure that you
are not causing any table scans for tables with a large number of records.
For small tables, the query optimizer may very well decide that a full table
scan is the most efficient query. I wouldn't worry too much about tables with
a small number of records, like say 50 or less.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________