Results 1 to 3 of 3
  1. #1
    2 Star Lounger
    Join Date
    Jan 2001
    Location
    Arlington, Texas, USA
    Posts
    124
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Database format (Access 2000)

    This is a general format question. I am developing a business application for a small business. There will be (at this point) three departments covered by this app. I want to have a central screen or main menu that branches to all three departments. My question is should I build three different databases called or controlled by a VB menu, or just build one db and insure that the naming conventions identify the departments that use the specific objects?

    Thanks
    shihaud

  2. #2
    3 Star Lounger
    Join Date
    Jan 2001
    Location
    Brisbane, Queensland, Australia
    Posts
    352
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Database format (Access 2000)

    I would say definitely one DB. Otherwise you will get differences and maintaining will be a nightmare. Set up a table with two fields: DeptID (Autonumber Primary Key) and Department Name. Then include DeptID as a long with a forced one to many relationship in other relevant tables. In your forms you can use this field in your query or filter, when you want to see just one dept.
    David Grugeon
    Brisbane Australia

  3. #3
    2 Star Lounger
    Join Date
    Jan 2001
    Location
    Arlington, Texas, USA
    Posts
    124
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Database format (Access 2000)

    Thanks I will approach it that way, it makes since to keep it all under one roof.
    shihalud

Posting Permissions

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