(Msg. 1) Posted: Sun Oct 04, 2009 1:44 am
Post subject: Does Access Support Concurrent Users? Archived from groups: microsoft>public>access>gettingstarted (more info?)
Hi everyone
I am trying to help a friend create a new work flow for his office. I would
like to build him a custom application that he and his employees can use to
access and manage their data. My question relates to how concurrent users
would access an Access database?
I was thinking of a creating an Access file that had data about their
customers, as well as internal links to other documents of the clients, a
main menu switchboard as a starting place, forms and reports, and automation.
I would then store this application (is it just an Access file) on the
office's server, and each employee could open the file and work from it.
What happens when all 5 employees are working from the file at once? what
happens if one person alters or creates data in the file? Can i restrict
some parts of the application to certain users? thanks a lot for any help.
Windows and Office is foreign ground for me.
(Msg. 2) Posted: Sun Oct 04, 2009 5:27 am
Post subject: Re: Does Access Support Concurrent Users? [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Here's a response to the first question...
Out of the box, Access is designed to support multiple users.
However, having everyone trying to 'hit' the same file on the network at the
same time is almost surely guaranteed to result, sooner or later, in
corruption, and will degrade network performance and make
maintenance/upgrade difficult.
Instead, the common approach to building Access applications is to put all
the data in one Access database, out on your network. The rest (forms,
queries, etc.) goes into a second Access database.
Link that second Access database to the tables/data in the one on the
network. Then put a copy of that second db on EACH user's desktop/PC.
This is called "splitting", and reduces the problems noted above.
Good luck!
--
Regards
Jeff Boyce
Microsoft Access MVP
"minofifa" <minofifa.RemoveThis@discussions.microsoft.com> wrote in message
news:D8207AC1-73D0-46D8-ABC3-DB08DB94610B@microsoft.com...
> Hi everyone
>
> I am trying to help a friend create a new work flow for his office. I
> would
> like to build him a custom application that he and his employees can use
> to
> access and manage their data. My question relates to how concurrent users
> would access an Access database?
>
> I was thinking of a creating an Access file that had data about their
> customers, as well as internal links to other documents of the clients, a
> main menu switchboard as a starting place, forms and reports, and
> automation.
> I would then store this application (is it just an Access file) on the
> office's server, and each employee could open the file and work from it.
> What happens when all 5 employees are working from the file at once? what
> happens if one person alters or creates data in the file? Can i restrict
> some parts of the application to certain users? thanks a lot for any
> help.
> Windows and Office is foreign ground for me.
>
>
(Msg. 3) Posted: Sun Oct 04, 2009 11:53 am
Post subject: Re: Does Access Support Concurrent Users? [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Jeff given you a great answer.
I have an article that explains how to setup and use ms-access in a
multi-user environment:
(Msg. 4) Posted: Sun Oct 04, 2009 2:35 pm
Post subject: Re: Does Access Support Concurrent Users? [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
And to answer this part of the question:
minofifa wrote:
> Can i restrict some parts of the
> application to certain users? thanks a lot for any help. Windows and
> Office is foreign ground for me.
Yes, either create separate front-end applications for each user, or you
need to use the MDB format so that you can secure your database and give
permissions to each user. The second choice is by far better, but there's
more to learm. Here's where you can learn some security information:
(Msg. 5) Posted: Sun Oct 04, 2009 2:35 pm
Post subject: Re: Does Access Support Concurrent Users? [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Awesome, thanks everyone for the resources. I really appreciate it.
I have one more question, and this may induce many of you to ream me out for
being incredibly ignorant but...
I have been reading a bit about windows server 2008 but it seems to me that
a lot of the functions it provides can be more easily implemented using a
sophisticated router. Our project is small so things like DNS, WINS, DHCP
etc are overkill. I am leaning towards a solution where the office computers
are connected with a single router, and one will act as a file sever,
providing access to my MS Access backend. This server would probably only
need to run Windows 7. the server would also hold all of the office's excel
and word files (which would be accessed through the Access application via
separate front ends deployed on each user's computer.
Any advice would be much appreciated ( and I will be going through all of
the great resources provided so far). Thanks again.
(Msg. 6) Posted: Sun Oct 04, 2009 3:08 pm
Post subject: Re: Does Access Support Concurrent Users? [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
On Sun, 4 Oct 2009 12:36:09 -0700, minofifa
<minofifa.TakeThisOut@discussions.microsoft.com> wrote:
>I have been reading a bit about windows server 2008 but it seems to me that
>a lot of the functions it provides can be more easily implemented using a
>sophisticated router. Our project is small so things like DNS, WINS, DHCP
>etc are overkill. I am leaning towards a solution where the office computers
>are connected with a single router, and one will act as a file sever,
>providing access to my MS Access backend. This server would probably only
>need to run Windows 7. the server would also hold all of the office's excel
>and word files (which would be accessed through the Access application via
>separate front ends deployed on each user's computer.
This isn't really an Access question, but more of a Windows issue. You can
certainly use Windows Server 2008 for this purpose, but from your description
it's overkill: you could perfectly well use a peer to peer network of
computers running Windows 7, Windows Vista, Windows XP, even Windows 98 if
you're stuck that far back. An Access database does NOT need to be "on a
Server" and you do not need to worry about DNS, etc. - the networking
capabilities of Windows can deal with all that for you.
Granted, if you want to get under the hood and set up group policies, control
your networking architecture, etc. you certainly can - my point is that it is
not *necessary* to do so in order to have a shared Access database.
--
(Msg. 7) Posted: Sun Oct 04, 2009 5:10 pm
Post subject: Re: Does Access Support Concurrent Users? [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Hello,
All you need do is put the backend (Access file containing only the data
tables) on the file server and give each user a copy of the frontend file
(Access file containg the application - queries, forms, reports and modules
if any). Obviously, each user must be able to connect to the file server.
As far as Windows 7 is concerned, Windows XP is a very reliable standard. It
would be a good choice for your implementation.
You mention "....... the server would also hold all of the office's excel
and word files ......", there is no doubt that there are opportunities to
automate how these files are being used and in fact, these files might be
integrated with Access or even further, especially Excel files, what is
being done could be better done in Access. I provide help with Access, Excel
and Word applications for a small fee. I could help you look at the forest
and develop a strategy and implementation that significantly improves the
efficiency of the current system. If you are interested, contact me.
Steve
santus.DeleteThis@penn.com
"minofifa" <minofifa.DeleteThis@discussions.microsoft.com> wrote in message
news:849819F5-DAB5-4B0B-ACD1-55451A576784@microsoft.com...
> Awesome, thanks everyone for the resources. I really appreciate it.
>
> I have one more question, and this may induce many of you to ream me out
> for
> being incredibly ignorant but...
>
> I have been reading a bit about windows server 2008 but it seems to me
> that
> a lot of the functions it provides can be more easily implemented using a
> sophisticated router. Our project is small so things like DNS, WINS, DHCP
> etc are overkill. I am leaning towards a solution where the office
> computers
> are connected with a single router, and one will act as a file sever,
> providing access to my MS Access backend. This server would probably only
> need to run Windows 7. the server would also hold all of the office's
> excel
> and word files (which would be accessed through the Access application via
> separate front ends deployed on each user's computer.
>
> Any advice would be much appreciated ( and I will be going through all of
> the great resources provided so far). Thanks again.
>
> "Arvin Meyer [MVP]" wrote:
>
>> And to answer this part of the question:
>>
>> minofifa wrote:
>> > Can i restrict some parts of the
>> > application to certain users? thanks a lot for any help. Windows and
>> > Office is foreign ground for me.
>>
>> Yes, either create separate front-end applications for each user, or you
>> need to use the MDB format so that you can secure your database and give
>> permissions to each user. The second choice is by far better, but there's
>> more to learm. Here's where you can learn some security information:
>>
>> Security FAQ
>> http://support.microsoft.com/download/support/mslfiles/SECFAQ.EXE >>
>> Lynn Trapp's summarization:
>> http://www.ltcomputerdesigns.com/The10Steps.htm >>
>> KB articles:
>> http://support.microsoft.com/default.aspx?scid=KB;en-us;q165009 >> http://download.microsoft.com/download/access97/faq1/1/win98/en-us/secfaq.exe >> http://support.microsoft.com/default.aspx?kbid=325261 >>
>> Joan Wild's articles:
>> http://www.jmwild.com/security02.htm >> http://www.jmwild.com/security97.htm >> http://www.jmwild.com/SecureNoLogin.htm >> http://www.jmwild.com/Unsecure.htm >> --
>> Arvin Meyer, MCP, MVP
>> http://www.datastrat.com >> http://www.mvps.org/access >> http://www.accessmvp.com >>
>>
>>
(Msg. 8) Posted: Sun Oct 04, 2009 6:05 pm
Post subject: Re: Does Access Support Concurrent Users? [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
=?Utf-8?B?bWlub2ZpZmE=?= <minofifa.TakeThisOut@discussions.microsoft.com> wrote
in news:849819F5-DAB5-4B0B-ACD1-55451A576784@microsoft.com:
> I have been reading a bit about windows server 2008 but it seems
> to me that a lot of the functions it provides can be more easily
> implemented using a sophisticated router. Our project is small so
> things like DNS, WINS, DHCP etc are overkill.
Um, you may not need a dedicated Windows server to act as DNS, WINS
and DHCP server, but your workstations do need at least DNS, and if
you're using dynamically-assigned IP addresses, there has to be a
DHCP server.
In general, your router (not your Windows server) would provide the
DHCP services, and DNS would be provided for the Internet via the
router.
For a peer-to-peer LAN, if you have no local DNS or WINS server to
keep track of the names and IP addresses of the machines inside your
local LAN, you will have to enabled NETBIOS over TCP/IP. That is
not, I believe, the default setting any longer. What it does is use
broadcast packets to figure out which machine name correspondes to
each TCP/IP address. In a small office network with a proper
firewall (your router probably acts as firewall, and if you're using
Network Address Translation (i.e., NAT), your local addresses are
unroutable and can't be reached from outside your router, anyway),
NETBIOS over TCP/IP is OK.
Without the local DNS and WINS servers, you won't be able to use
machine names, and will instead have to use IP addresses for the
workstations to communicate with each other.
> I am leaning towards a solution where the office computers
> are connected with a single router, and one will act as a file
> sever, providing access to my MS Access backend.
This sounds fine, as long as you have your NETBIOS over TCP/IP
setting correct.
> This server would probably only
> need to run Windows 7.
Why? It could run any version of Windows workstation. While Windows
7 is quite a nice workstation OS, I'm not sure that it is a better
server, so I see no reason to privilege it over any other version.
If I had a choice between WinXP, Vista and Windows 7, I'd probably
put them in this order of descending desirability to function as
peer-to-peer server:
1. WinXP
2. Windows 7
3. Vista
The reason for Vista coming in last is that it's less efficient than
Windows 7, and because it has had problems with certain new
networking settings (they got them right in Windows 7, though).
Also, you need to consider the speed of the workstation (more CPU
cycles is better), the amount of RAM (more is better), and the disk
storage (more is better, faster drives are better). So, you might
end up with a sub-optimal choice on OS because the hardware is much
better on the machine with the newer OS.
> the server would also hold all of the office's excel
> and word files (which would be accessed through the Access
> application via separate front ends deployed on each user's
> computer.
This sounds right.
However, keep in mind that it's not ideal to be using a workstation
as a peer-to-peer server, particularly if that workstation gets
heavy use.
All times are: Eastern Time (US & Canada) (change) Goto page 1, 2
Page 1 of 2
You can post new topics in this forum You can reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum