Results 1 to 7 of 7
  1. #1
    Join Date
    Aug 2003
    Location
    UK
    Posts
    78

    Unanswered: Database Splitting

    I read, "You should always split your databases". What does this mean?

    I have a suspicion but I don’t know.

    I am building a database that will soon be deployed, but I will be continuously adding new features and functionality. How is the best way to achieve a stable on-going use of my current system whilst gradually introducing the changes, some big changes some small changes, without disturbing the stored data. Does splitting come into this?
    the light is on, someone is home, but they dont know they are. HELLO!

  2. #2
    Join Date
    Oct 2003
    Location
    São Paulo - Brazil
    Posts
    91

    Re: Database Splitting

    Originally posted by dapman2002
    I read, "You should always split your databases". What does this mean?

    I have a suspicion but I don’t know.

    I am building a database that will soon be deployed, but I will be continuously adding new features and functionality. How is the best way to achieve a stable on-going use of my current system whilst gradually introducing the changes, some big changes some small changes, without disturbing the stored data. Does splitting come into this?
    When you split a database, you´ll have 2 mdb:

    Front-end: With forms, queries, reports, etc. Each client machine has a copy of it.

    Back-End: With tables, and perhaps, queries (depending on your needs). Usually, usally stays in the server.

    The goal of splitting the application is to reduce data traffic in the net.

    One way to minimize troubles of development, is to have versions of the software. Your beta-test user will have the latest version of the Front-End. The others will have the older one.
    My environment: Windows XP/ Access 2000 - Using Microsoft DAO 3.6 Library

  3. #3
    Join Date
    Aug 2003
    Location
    UK
    Posts
    78

    Re: Database Splitting

    Thank you that makes perfect sense.
    the light is on, someone is home, but they dont know they are. HELLO!

  4. #4
    Join Date
    Aug 2003
    Location
    UK
    Posts
    78

    Re: Database Splitting

    One more question. Having split the DB do I get them to talk by linking the table from one to another?
    the light is on, someone is home, but they dont know they are. HELLO!

  5. #5
    Join Date
    Oct 2003
    Location
    São Paulo - Brazil
    Posts
    91

    Re: Database Splitting

    Originally posted by dapman2002
    One more question. Having split the DB do I get them to talk by linking the table from one to another?
    Yes. You have to link your table in each Front-end

    In my application, I have a Back-end with all table: from clients to suppliers, from parts to materials, etc. Then, the application (Front-End) who needs a table, have to link it.

    Pay close atention: You have to LINK tables. Don´t IMPORT then
    My environment: Windows XP/ Access 2000 - Using Microsoft DAO 3.6 Library

  6. #6
    Join Date
    Aug 2003
    Location
    UK
    Posts
    78

    Re: Database Splitting

    Originally posted by Mixirica
    Yes. You have to link your table in each Front-end

    In my application, I have a Back-end with all table: from clients to suppliers, from parts to materials, etc. Then, the application (Front-End) who needs a table, have to link it.

    Pay close atention: You have to LINK tables. Don´t IMPORT then
    I am creating SQL queries on the fly so I guess i will have to generate those at the forms on the users machines. Most of the queries require choices from the user.
    the light is on, someone is home, but they dont know they are. HELLO!

  7. #7
    Join Date
    Oct 2003
    Location
    São Paulo - Brazil
    Posts
    91

    Re: Database Splitting

    Originally posted by dapman2002
    I am creating SQL queries on the fly so I guess i will have to generate those at the forms on the users machines. Most of the queries require choices from the user.
    That´s it !
    My environment: Windows XP/ Access 2000 - Using Microsoft DAO 3.6 Library

Posting Permissions

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