Transfer Records Between 2 Back-Ends

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ahd2008
    New Member
    • Nov 2008
    • 68

    #1

    Transfer Records Between 2 Back-Ends

    Hi everyone,

    Hope someone can help with my issue. I have two back-ends that I use for my tracking system. Now, I need to transfer one table records (not all the records, some records) from one back-end to the other.

    Can anyone enlighten me how to accomplish this?

    Take into consideration that both of the back-ends are protected with password and the transfer should be done through the front-end (by clicking a button)?

    Thanks in advance
  • ADezii
    Recognized Expert Expert
    • Apr 2006
    • 8834

    #2
    Here is how I would approach the problem:
    1. Open up the External (Back End) Databases via DAO or ADO.
    2. Pass the Password (no pun intended) when opening the DBs. In DAO, you would provide the Password in the Options Argument of the OpenDatabase() Method. In ADO, you would provide it within the Connection String or as a Property of the Connection Object.
    3. Now that both DBs are 'Opened', create the appropriate Recordsets for both Back End DBs.
    4. Transfer Records from one Recordset to another by using the AddNew...Update Methods of the Recordset that will be receiving Records.
    5. Keep in mind that both DBs should be opened Exclusively in order to avoid any potential Conflicts.

    Comment

    • NeoPa
      Recognized Expert Moderator MVP
      • Oct 2006
      • 32669

      #3
      Please understand that this is not an adequate question, but looks more like a simple request for work. ADezii's response is quite appropriate as it stands, but please understand that any further detailed help is against our rules unless/until you show the work that you've done on this. I'm sure ADezii will be more than happy to go further if you get stuck, but any request for more detailed help which doesn't include good indication that you are attempting to follow this advice yourself is likely to be removed. You're experienced enough now to be expected to know this, but this question was definitely borderline.

      As for the question itself, I would just comment that ADezii's point #5 should not be necessary. That is not to say it's a bad idea if you can get away with it, but there are other alternatives (such as Workspace Transactions) that would also be adequate.

      My own advice would also be to use SQL rather than recordsets, as I believe the whole process could be handled in one go, but again, that is my preference. ADezii's advice is certainly a correct solution.
      Last edited by NeoPa; Feb 17 '13, 08:16 PM.

      Comment

      • ahd2008
        New Member
        • Nov 2008
        • 68

        #4
        Sorry for the late reply. Thanks ADezil that sounds a great approach; I have followed the steps and it worked

        Neopa, I wasn't looking for detailed answers. I just wanted to know how to complete this task in the right manner as I had no clue about working with two different back-ends.

        Thanks all

        Comment

        Working...