A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

msAccess capacity



 
 
Thread Tools Display Modes
  #1  
Old November 7th, 2008, 01:54 AM posted to microsoft.public.access.tablesdbdesign
hpoincare
external usenet poster
 
Posts: 12
Default msAccess capacity

I'm intent on using access to manage inventory, trouble tickets, contacts,
and events for a company with 500 users.

Am I asking too much of Access? There will only be about 5 to 10 techs
making entries and I expect to switch to SQL once I have a feel for it but
right now Access is enough of a challenge.

Assuming we have about 50 new records each week - is this practical?
  #2  
Old November 7th, 2008, 03:32 AM posted to microsoft.public.access.tablesdbdesign
hpoincare
external usenet poster
 
Posts: 12
Default msAccess capacity

I found the answers to my questions in the following link

http://www.members.shaw.ca/AlbertKallal/Wan/Wans.html

Thanks Albert!

"hpoincare" wrote:

I'm intent on using access to manage inventory, trouble tickets, contacts,
and events for a company with 500 users.

Am I asking too much of Access? There will only be about 5 to 10 techs
making entries and I expect to switch to SQL once I have a feel for it but
right now Access is enough of a challenge.

Assuming we have about 50 new records each week - is this practical?

  #3  
Old November 7th, 2008, 07:33 AM posted to microsoft.public.access.tablesdbdesign
Daniel Pineault
external usenet poster
 
Posts: 658
Default msAccess capacity

You could have 2 000 000 users in your company, what is important is the
number of people actually entering data. You state 5-10 techs; Access can
handle this with ease. As for 50 new records a weeks, this too is not a
problem. You don't mention which version of Access you might use in your
devlopment but take a look at
http://office.microsoft.com/en-us/ac...868081033.aspx for some specs
on what Access can handle. If you read through some posts on this forum
you'll see mention of people that have dbs with millions of entries without
any issues, so yes Access can handle your needs, based on what you have
stated thus far.

The key to developing a multi-user system like the one your are talking
about is to create you db, secure it, split it and then distribute a
front-end copy to each user.
--
Hope this helps,

Daniel Pineault
http://www.cardaconsultants.com/
For Access Tips and Examples: http://www.devhut.net
Please rate this post using the vote buttons if it was helpful.



"hpoincare" wrote:

I found the answers to my questions in the following link

http://www.members.shaw.ca/AlbertKallal/Wan/Wans.html

Thanks Albert!

"hpoincare" wrote:

I'm intent on using access to manage inventory, trouble tickets, contacts,
and events for a company with 500 users.

Am I asking too much of Access? There will only be about 5 to 10 techs
making entries and I expect to switch to SQL once I have a feel for it but
right now Access is enough of a challenge.

Assuming we have about 50 new records each week - is this practical?

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 07:08 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.