Welcome to SPN

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

Sign Up Now!

Converted Database is replicating itself

Discussion in 'Information Technology' started by Marte Cabello, Nov 1, 2005.

  1. Marte Cabello

    Marte Cabello
    Expand Collapse
    Guest

    Hi All,

    We generated an Access 97 database some years ago, and we handle very
    important information with it.. We are in the process of updating it to
    Access 2000, but when we thought it was ready, as soon as the users started
    accessing it, it would generate sequential copies (db1, db2, etc...) of
    itself.

    This database was updated in a computer that had only Access 2000, but the
    users have both Access 97 and Access 2000 in the same computer.

    Could the replication be caused by having both versions in the same
    computer, is there any other option I should look at? How can I fix this?

    Thanks in advance and kind regards
    --
    Marte Cabello
     
  2. Loading...

    Similar Threads Forum Date
    Islam Ishna Has Converted To Islam Interfaith Dialogues Apr 1, 2016
    Guru Granth Sahib Converted.... Essays on Sikhism Oct 4, 2011
    How to tie a patka and turban - converted sikh Sikh Youth May 5, 2010
    Sikh News Converted Sikh should be buried, says Shariah court (rediff.com) Breaking News Jun 5, 2009
    Heritage Radio Pakistan says Sikhs in India are Forcibly Converted History of Sikhism Apr 6, 2009

  3. '69 Camaro

    '69 Camaro
    Expand Collapse
    Guest

    Hi, Marte.

    Is this an unsplit, shared database located on a networked server? Is the
    "Compact on close" option set? If so, the database is attempting to compact
    the database when someone exits the application, but can't because others
    still have the database open. Split the database into a front end (queries,
    forms, modules, et cetera) and a back end (tables and relationships only).
    Place the back end on the networked server, and place a copy of the front end
    on each user's workstation. Users should not be sharing the front end -- or
    a single database file on the network, either.

    HTH.
    Gunny

    See http://www.QBuilt.com for all your database needs.
    See http://www.Access.QBuilt.com for Microsoft Access tips.

    (Please remove ZERO_SPAM from my reply E-mail address so that a message will
    be forwarded to me.)
    - - -
    If my answer has helped you, please sign in and answer yes to the question
    "Did this post answer your question?" at the bottom of the message, which
    adds your question and the answers to the database of answers. Remember that
    questions answered the quickest are often from those who have a history of
    rewarding the contributors who have taken the time to answer questions
    correctly.


    "Marte Cabello" wrote:

    > Hi All,
    >
    > We generated an Access 97 database some years ago, and we handle very
    > important information with it.. We are in the process of updating it to
    > Access 2000, but when we thought it was ready, as soon as the users started
    > accessing it, it would generate sequential copies (db1, db2, etc...) of
    > itself.
    >
    > This database was updated in a computer that had only Access 2000, but the
    > users have both Access 97 and Access 2000 in the same computer.
    >
    > Could the replication be caused by having both versions in the same
    > computer, is there any other option I should look at? How can I fix this?
    >
    > Thanks in advance and kind regards
    > --
    > Marte Cabello
     
  4. Marte Cabello

    Marte Cabello
    Expand Collapse
    Guest

    Hi Gunny,

    You're right, it's a single database shared in a network folder with the
    Compact on Close option on. We will work in splitting the application, so
    thank you for your answer, and specially for being so fast.

    Kind regards.
    --
    Marte Cabello


    "'69 Camaro" wrote:

    > Hi, Marte.
    >
    > Is this an unsplit, shared database located on a networked server? Is the
    > "Compact on close" option set? If so, the database is attempting to compact
    > the database when someone exits the application, but can't because others
    > still have the database open. Split the database into a front end (queries,
    > forms, modules, et cetera) and a back end (tables and relationships only).
    > Place the back end on the networked server, and place a copy of the front end
    > on each user's workstation. Users should not be sharing the front end -- or
    > a single database file on the network, either.
    >
    > HTH.
    > Gunny
    >
    > See http://www.QBuilt.com for all your database needs.
    > See http://www.Access.QBuilt.com for Microsoft Access tips.
    >
    > (Please remove ZERO_SPAM from my reply E-mail address so that a message will
    > be forwarded to me.)
    > - - -
    > If my answer has helped you, please sign in and answer yes to the question
    > "Did this post answer your question?" at the bottom of the message, which
    > adds your question and the answers to the database of answers. Remember that
    > questions answered the quickest are often from those who have a history of
    > rewarding the contributors who have taken the time to answer questions
    > correctly.
    >
    >
    > "Marte Cabello" wrote:
    >
    > > Hi All,
    > >
    > > We generated an Access 97 database some years ago, and we handle very
    > > important information with it.. We are in the process of updating it to
    > > Access 2000, but when we thought it was ready, as soon as the users started
    > > accessing it, it would generate sequential copies (db1, db2, etc...) of
    > > itself.
    > >
    > > This database was updated in a computer that had only Access 2000, but the
    > > users have both Access 97 and Access 2000 in the same computer.
    > >
    > > Could the replication be caused by having both versions in the same
    > > computer, is there any other option I should look at? How can I fix this?
    > >
    > > Thanks in advance and kind regards
    > > --
    > > Marte Cabello
     
  5. John Vinson

    John Vinson
    Expand Collapse
    Guest

    On Mon, 31 Oct 2005 09:25:19 -0800, "Marte Cabello"
    <MarteCabello@discussions.microsoft.com> wrote:

    >Hi All,
    >
    >We generated an Access 97 database some years ago, and we handle very
    >important information with it.. We are in the process of updating it to
    >Access 2000, but when we thought it was ready, as soon as the users started
    >accessing it, it would generate sequential copies (db1, db2, etc...) of
    >itself.
    >
    >This database was updated in a computer that had only Access 2000, but the
    >users have both Access 97 and Access 2000 in the same computer.
    >
    >Could the replication be caused by having both versions in the same
    >computer, is there any other option I should look at? How can I fix this?
    >
    >Thanks in advance and kind regards


    The most likely reason is that the database has been set to Compact on
    Close; and that the users don't have Delete permission on the folder
    containing the database. The compaction process works by creating a
    new database named db1 (or db2 if there is a db1, etc.), copying
    everything into it, and renaming the db1 and deleting the old
    database.

    Check the users' permissions on the database folder: they need full
    create, edit, delete permission.

    John W. Vinson[MVP]
     
  6. '69 Camaro

    '69 Camaro
    Expand Collapse
    Guest

    You're welcome. Once you split the database, you might be interested in
    automating the distribution of any new front ends with Tony Toews's (MVP)
    AutoFE utililty. With this utility, the developer places the new front end
    on the server and the next time the users open the application, the new
    front end is saved to their hard drives and they start using it. Please see
    the following Web page for more information on his utility:

    http://www.granite.ab.ca/access/autofe.htm

    HTH.
    Gunny

    See http://www.QBuilt.com for all your database needs.
    See http://www.Access.QBuilt.com for Microsoft Access tips.


    "Marte Cabello" <MarteCabello@discussions.microsoft.com> wrote in message
    news:3AC46262-9131-41C3-8EE6-29461FCA7C57@microsoft.com...
    > Hi Gunny,
    >
    > You're right, it's a single database shared in a network folder with the
    > Compact on Close option on. We will work in splitting the application, so
    > thank you for your answer, and specially for being so fast.
    >
    > Kind regards.
    > --
    > Marte Cabello
    >
    >
    > "'69 Camaro" wrote:
    >
    >> Hi, Marte.
    >>
    >> Is this an unsplit, shared database located on a networked server? Is
    >> the
    >> "Compact on close" option set? If so, the database is attempting to
    >> compact
    >> the database when someone exits the application, but can't because others
    >> still have the database open. Split the database into a front end
    >> (queries,
    >> forms, modules, et cetera) and a back end (tables and relationships
    >> only).
    >> Place the back end on the networked server, and place a copy of the front
    >> end
    >> on each user's workstation. Users should not be sharing the front end --
    >> or
    >> a single database file on the network, either.
    >>
    >> HTH.
    >> Gunny
    >>
    >> See http://www.QBuilt.com for all your database needs.
    >> See http://www.Access.QBuilt.com for Microsoft Access tips.
    >>
    >> (Please remove ZERO_SPAM from my reply E-mail address so that a message
    >> will
    >> be forwarded to me.)
    >> - - -
    >> If my answer has helped you, please sign in and answer yes to the
    >> question
    >> "Did this post answer your question?" at the bottom of the message, which
    >> adds your question and the answers to the database of answers. Remember
    >> that
    >> questions answered the quickest are often from those who have a history
    >> of
    >> rewarding the contributors who have taken the time to answer questions
    >> correctly.
    >>
    >>
    >> "Marte Cabello" wrote:
    >>
    >> > Hi All,
    >> >
    >> > We generated an Access 97 database some years ago, and we handle very
    >> > important information with it.. We are in the process of updating it to
    >> > Access 2000, but when we thought it was ready, as soon as the users
    >> > started
    >> > accessing it, it would generate sequential copies (db1, db2, etc...) of
    >> > itself.
    >> >
    >> > This database was updated in a computer that had only Access 2000, but
    >> > the
    >> > users have both Access 97 and Access 2000 in the same computer.
    >> >
    >> > Could the replication be caused by having both versions in the same
    >> > computer, is there any other option I should look at? How can I fix
    >> > this?
    >> >
    >> > Thanks in advance and kind regards
    >> > --
    >> > Marte Cabello
     

Share This Page