Results 1 to 5 of 5
  1. #1
    Join Date
    Feb 2004
    Location
    Irving, TX (Dallas, Fort Worth)
    Posts
    379

    Unanswered: Non-Replica Data Sync

    All,

    I've seen code around, like a tool library, that lets you sync data from any two external .mdb files.

    Does any one have a good link. I've tried Googling it, but must not be using the right key words.

    DBS4M

  2. #2
    Join Date
    Feb 2004
    Location
    Irving, TX (Dallas, Fort Worth)
    Posts
    379

    Sync outside of Replication

    All,

    From what I have been reading the DAO.synchronize works only if one has declared a REPLICATION SET. Am I right?

    I need to use sync in two very seperate and distinct ways:
    1. Code (Updating forms, modules, etc),
    2. Data.
    I can not intermingle the two and not sure if the TSI sync program I found will seperate them.

    Any suggestions?

    Thanks!

    DBS4M

  3. #3
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926
    The sync you're referring to might have to do with MSAccess Replication (which I'd avoid). You then get into a "Master" mdb file with "node" mdbs and synch the master with the nodes (data and/or code). You also get into all kinds of other things with replication like the "Star" model, etc... It all becomes messy with Replication and it's usually more problematic than what it's worth (I've seen many failed replication models and have really never seen it work without some sort of problem.)

    Problems with Replication...
    1. Anyone with a slow connection to where the "Master" mdb resides will have problems synchranizing (data and/or code). It usually bombs out in the process and destroys the node mdb in which case you have to setup another node mdb for them.
    2. Synching can be EXTREMELY slow! (even with the smallest dataset.)
    3. Master mdb can EASILY be destroyed and the only way to restore the Master mdb is via a backup.
    4. Code synching rarely works (since you usually need to compile the code after synching which replication doesn't do very well.)
    5. Basically Replication is just one big pain in the #$$ to work with and once you do it, you're stuck down that path (unless again, you go to an unreplicated backup.)

    Instead of trying a Replication type process (which again, once you replicate an mdb, there's no turning back unless you go to an unreplicated backup), I might suggest you have users connect to the source mdb via citrx, terminal server, vpn, or however it's setup for external users to connect into the network system (since they'd have to connect anyway to do the synching). Then you only have to worry about one source mdb and not synching it up to all the nodes. - ie. Everyone would connect into the network (however they do it), and then go to where you store the mdb on the network and launch it. ANYTHING else is better than Replicating an mdb!

    If you need to transfer/update data from one mdb to another, I'd personally just link in the tables from both mdb's into 1 mdb and write a few queries to do it (automating it if necessary - ie. have the queries run automatically when the mdb is launched and schedule the mdb to run in Task Scheduler).

    As far as synching code, I have to ask why do you need to do that before answering? (but you could probably automate importing the forms, reports, etc. from one mdb into another - although I personally wouldn't go through the hassle of coding this since there are better ways!)
    Last edited by pkstormy; 05-30-09 at 01:06.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

  4. #4
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    I've forgotten how to even do it once I figured out how bad it was. I'm surprised people still use it
    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

  5. #5
    Join Date
    Feb 2004
    Location
    Irving, TX (Dallas, Fort Worth)
    Posts
    379

    Project under development

    ST and All,

    Hey desperately need it, have large project, in Phase II with daily updates to code, so need one process for code sync to FE and need to re-sync data from production BE to dev/test box for accurate testing as some test are for data accuracy.

    Right now just using copy with overwrite for front-end, but have another programmer on this, so really need to be able to sync, not copy.

    Lady at the client handling the data can really get it wrong when coding shows us need for changes to tables, and getting all the data from an old table correctly back into the new table structure. Have to make the 3 hour trip to customer twice a week just to keep it in order.

    Thanks!

    DBS4M
    Last edited by dbsupport4me; 06-11-09 at 14:54.

Posting Permissions

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