Results 1 to 3 of 3
  1. #1
    nguyeda is offline Novice
    Windows Vista Access 2007
    Join Date
    Jun 2011
    Posts
    21

    Mulit-User Querying Database 250 people

    Hello,

    I have a HUGE access database with 20 or so queries. After the queries run, it exports to excel then I send it out to everyone myself.

    Well now we want people to be able to have access to the database, update the source data and view the queries.

    Is there a way through SQL, OLAP, Visual Studio or something else that can allow me to have people access a form from a shared intra-network to query my queries?

    The point is, I'm trying to figure out how to create a user friendly, multi-user database.



    Does anyone here have any experience and can share some stories or suggestions?

  2. #2
    June7's Avatar
    June7 is offline VIP
    Windows XP Access 2010 32bit
    Join Date
    May 2011
    Location
    The Great Land
    Posts
    52,815
    First thing you need to do is split the database, if not already, into frontend and backend files. Frontend links to tables in backend. Frontend has queries, forms, reports, code. Users open frontend.

    250 users is a lot for Access. Might consider MYSQL or SQLExpress as the backend.
    How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.

  3. #3
    orange's Avatar
    orange is offline Moderator
    Windows XP Access 2003
    Join Date
    Sep 2009
    Location
    Ottawa, Ontario, Canada; West Palm Beach FL
    Posts
    16,716
    Further to June7's advice, I think you may want to step back a bit and consider what you are doing. Do you have some process/procedure for development? Do you understand testing? Do you understand maintenace? Do you have any form or procedure for communicating what the new application is for, who will use it? How? when? How changes and feedback will be done??

    Do you have Access on 250 machines? And Excel (for whatever reason)?

    Before you send an application to 250 users, there are some basics that must be considered. Splitting FE/BE is fundamental-- but other DBMS may be more practical.

    An application with 20 queries is not HUGE, necessarily.
    Trying to "send" an Access application to 250 users is a potential disaster. If this is your first attempt at a shared database implementation, you now may have more issues and problems than you can solve.

    It doesn't appear, from the info you provided, that SQL, OLAP or Visual Studio or any other software is the root issue.

    In any event, good luck with your project.

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Replies: 2
    Last Post: 01-31-2011, 10:17 AM
  2. Querying a database with optuion buttons
    By MattB in forum Access
    Replies: 1
    Last Post: 01-28-2010, 06:43 PM
  3. Replies: 0
    Last Post: 12-28-2009, 12:14 PM
  4. Best way to organize a small database of people?
    By Orabidoo in forum Database Design
    Replies: 1
    Last Post: 06-09-2009, 10:13 PM
  5. New Database - New User
    By mcarrigg in forum Database Design
    Replies: 1
    Last Post: 06-21-2008, 04:56 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums