How to stop Access 2007 user from corrupting an Access 2003 Databa

Discussion in 'Access Configuration' started by The_bald_head, Jan 21, 2010.

  1. Hi,

    I have an Access 2003 system with multiple corporate users with Office /
    Access 2003 installed.

    The company is going through an Office / Access upgrade to 2007, one person
    has been upgraded so far and everytime this person opens the system, they
    corrupt the database.

    Is there a workaround / add in / plug in that I or my user can install / do
    that will stop this from happening until I or the majority of my users are
    using 2007?

    Thanking you in anticpation.
     
    The_bald_head, Jan 21, 2010
    #1
    1. Advertisements

  2. The_bald_head

    Gina Whipp Guest

    The_bald_head,

    What I didn't *hear* was they all have their own FE. If that is the case,
    and they are sharing the same FE, then yes this will cause issues. The
    References are getting confused between the different versions. For help on
    splitting see...


    http://www.members.shaw.ca/AlbertKallal/Articles/split/

    http://allenbrowne.com/ser-01.html


    You may also want to take a look at MVP Tom Wickerath's article...

    http://www.accessmvp.com:80/TWickerath/articles/multiuser.htm


    To handle the update of multiple front ends see...

    http://www.autofeupdater.com/

    ....HOWEVER, if the FE is not the case please explain what you mean by
    corruption. Error messages?

    --
    Gina Whipp
    2010 Microsoft MVP (Access)

    "I feel I have been denied critical, need to know, information!" - Tremors
    II

    http://www.regina-whipp.com/index_files/TipList.htm
     
    Gina Whipp, Jan 21, 2010
    #2
    1. Advertisements

  3. Hi Gina,

    Splitting a "Mickey Mouse" Access system is too much hazzle and maintenance.

    What I have done to resolve this is to ensure both 2003 & 2007 users
    "Default File Format" is set to "Access 2002 - 2003".

    Thanks for trying to help.
     
    The_bald_head, Mar 4, 2010
    #3
  4. The_bald_head

    Gina Whipp Guest

    The_bald_head,

    However, even a *Mickey Mouse* front end will get confused because the
    References are trying to set to the version it's being opened by. Setting
    the *Default File Format* does nothing for the References.

    Each Access version has *Default* References... Access 2003 uses the
    Microsoft Access 11.0 Object Library and Access 2007 uses the Microsoft
    Access 12.0 Object Library. Nothing you set will change that. Think of it
    like two keys, one to your house and one to the neighbors house, while they
    may *look* the same there is a tiny little difference that causes only one
    key to work with it's prospective house. So you can either use the proper
    key with the correct house or expect problems.

    Please split your *Mickey Mouse* database. What you can do AND mind you I
    do not recommend this but you can at the very least, give the Access 2007
    Users one front end and the Access 2003 Users another front end. As for the
    maintenance part, have a look at this by Toney Toews...

    http://www.autofeupdater.com/

    It will take care of updating multiple front ends for when you have updates.

    --
    Gina Whipp
    2010 Microsoft MVP (Access)

    "I feel I have been denied critical, need to know, information!" - Tremors
    II

    http://www.regina-whipp.com/index_files/TipList.htm

    Hi Gina,

    Splitting a "Mickey Mouse" Access system is too much hazzle and maintenance.

    What I have done to resolve this is to ensure both 2003 & 2007 users
    "Default File Format" is set to "Access 2002 - 2003".

    Thanks for trying to help.
     
    Gina Whipp, Mar 4, 2010
    #4
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.