Results 1 to 7 of 7
  1. #1
    Star Lounger
    Join Date
    May 2004
    Posts
    81
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Deployment (Access 2000)

    Hello,
    I would like to ask the panel of experts what is the best deployment method for a small company of 10 employees. Replication?, Client-Server?. I don't have a SERVER. Right now I run Access from the Admistrators console

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 28 Times in 28 Posts

    Re: Deployment (Access 2000)

    Do you have a network?
    Can you estimate how many employees will be entering/editing data simultaneously? (Don't include users only viewing data)

  3. #3
    Star Lounger
    Join Date
    May 2004
    Posts
    81
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Deployment (Access 2000)

    Hans,
    I really appreciate your reply. I will have probally three people entering data and the rest viewing and yes I do have a network

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 28 Times in 28 Posts

    Re: Deployment (Access 2000)

    Access can handle 3 users entering data and others viewing data without problems.
    I recommend splitting the database into a backend containing only tables, and a frontend containing everything else, if you haven't done so already. See Why Split a Database? on <!profile=WendellB>WendellB<!/profile>'s website about why and how.
    Put the backend in a network folder and give all users full permissions on this folder.
    Give each user his/her own copy of the frontend. If you need to deploy a new frontend, modify one copy, then give each user a copy of that one. Note: this assumes that the users don't create queries, reports etc. in their own frontend.

  5. #5
    Star Lounger
    Join Date
    May 2004
    Posts
    81
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Deployment (Access 2000)

    Hans,
    I totally agree with you. But when I go to split the database it reports an error message saying that either there is a syntax error in the declarations section of a vb module or I do not have the wizard loaded and if the latter is the case I am asked to reload the project to fix the problem.
    As far as there being an syntax error in a VB module I only have one and it compiles fine. I am new to database deployment so any help is much appreciated. I just want to say that you are of great help Hans.

  6. #6
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 28 Times in 28 Posts

    Re: Deployment (Access 2000)

    It is not difficult to split the database manually:
    - Create a backup copy of your database, just to be on the safe side.
    - Create a new blank database.
    - Select File | Get External Data | Import...
    - Locate and open your database.
    - Select all tables, but no other database objects (queries etc.), and click OK.
    - Close the new database (it will become the back end).
    - Open the original database.
    - Delete the tables, one by one.
    - Select File | Get External Data | Link Tables...
    - Locate and open the new database.
    - Select all tables, and click OK.
    - Select Tools | Database Utilities | Compact and Repair Database.
    - This database will become the master copy of the frontend.

  7. #7
    Star Lounger
    Join Date
    May 2004
    Posts
    81
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Deployment (Access 2000)

    Hans,
    D'oh. Sometimes I look for the hardest way to do something and when there is a very simple way to complete the same task. I appreciate all of your help as always. Thank you.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •