Results 1 to 5 of 5

Thread: Master/Slave

  1. #1
    Join Date
    Apr 2008
    Location
    Ireland
    Posts
    12

    Unanswered: Master/Slave

    I'm working with an antiquated version of 1997 Access for historical reasons as my company has most of its specialised databases on that version of Access. I wish to make a master slave format to this application as i spent hours trying to remedy today because someone messed around with it.

    I've tried the replication tool, but will that update the slave version or will the slave version need to be updated everytime the master is? Is this function better in newer versions of access. Or is there a better way to go about this problem. Any help would be much appreciated.

    Kind Regards

  2. #2
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926
    Avoid MSAccess Replication! Especially with Access 97! (although it is much better in later versions of Access but still problematic.) It is definately not the solution to find/prevent someone from "messing" around with your app.

    A better way would be using something like Citrix and have your users connect via Citrix and use the mdb. Consider also making an MDE file to prevent code tampering (you can't make code changes in an mde file).

    Why not replication? Access replication is slow (synchranizing data and programming changes), problematic (especially when connections are lost while synchranizing and especially problematic for dial-up connections), difficult to maintain table relationships with (ie. randomization of large autonumbers), difficult to maintain programming changes with (ie. Master/Slaves), and especially difficult to reverse once you've done it (keep backups BEFORE you replicate!)
    Last edited by pkstormy; 04-14-08 at 18:01.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

  3. #3
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Agreed with the MDE suggestion... and, of course, split the databases if they aren't already split.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  4. #4
    Join Date
    Apr 2008
    Location
    Ireland
    Posts
    12
    The databases are split. The problem with loading it on citrix is its a custom made application that they've been using this system for a few years and when you move it's location even when you change the hard code it becomes lets just say highly uncooperative!

    I will mess around with a few ideas. I was testing the master slave thing and it seemed fairly finicky, I will request to convert it to a newer version of access or at least see if I can change it over without too much debugging.

  5. #5
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926
    One reason to avoid hard-coding in any locations in vba. Not good programming practice. You should always have an mdb that you can move without having to modify code (if locations need to be put in the vba code, they should be done in a lookup type table where you only have to change the location in the table, not search through the code for locations.) Then you'd lookup the location value in vba to the lookup table.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

Posting Permissions

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