Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Making a copy of the current database using code

Discussion in 'Information Technology' started by Janelle.Dunlap@ge.com, Jul 28, 2006.

  1. Janelle.Dunlap@ge.com

    Janelle.Dunlap@ge.com
    Expand Collapse
    Guest

    In the database that I am creating I need to be able to rename the file
    with a name that the user specifies using the Save As Dialog window (I
    already have the code that brings up this window). In other words, I
    need to write code that makes a copy of the current database and saves
    it with a new name. I've read that it is a bad idea to copy a file
    that is currently in use so I am at a loss of what I should do. Any
    suggestions?
     
  2. Loading...

    Similar Threads Forum Date
    Partition 1947 - The Making Of Refugees History of Sikhism Mar 18, 2015
    Making The Change With Hope & Faith - Sikh Advocate Prabhjot Singh, Md Sikh Youth Mar 11, 2015
    Heritage Sikhs making Their History in Malaysia History of Sikhism May 18, 2013
    Inspirational Making a Difference: A School for Girls in Kenya Videos Mar 25, 2013
    Canada Star-struck’ security and limo drivers? Businesses complain TOIFA staff are making racist demands Breaking News Mar 18, 2013

  3. Albert D.Kallal

    Albert D.Kallal
    Expand Collapse
    Guest

    >I've read that it is a bad idea to copy a file
    > that is currently in use so I am at a loss of what I should do.


    You are quite correct. However, is your application under current
    development? Is your application planned to be multi-user?

    If you are continuing to develop your application, and it *currently* being
    used, then why not consider splitting your application.

    if your application is split, then it is a simple matter to have some code
    "copy" the data part out, and check if no one is currently in the database
    while you do this process.

    So, my suggestion is to spilt. It solves the problem of backing up the data
    (and, you can easily make a menu item to do this). It solves the problem of
    being able to work on one version while users are working on the existing
    version. It also increases stable in a multi-user environment.

    All in all, splitting your application will solve quite a few issues.

    You can read about splitting here:

    http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm
    --
    Albert D. Kallal (Access MVP)
    Edmonton, Alberta Canada
    pleaseNOOSpamKallal@msn.com
    http://www.members.shaw.ca/AlbertKallal
     
  4. Janelle.Dunlap@ge.com

    Janelle.Dunlap@ge.com
    Expand Collapse
    Guest

    Thanks, I'll try this.
     
  5. aaron.kempf@gmail.com

    aaron.kempf@gmail.com
    Expand Collapse
    Guest

    i would reccomend using a real engine like SQL Server. using Access
    Data Projects you can take a backup of the data while someone has the
    application open.
    this just isn't possible in mdb.

    the other thing to remember about mdb is that you have to copy / sync
    queries.
    with ADP all the queries are stored in one place-- where they should
    be-- the db server
     

Share This Page