Results 1 to 13 of 13
  1. #1
    JeanieMB is offline Novice
    Windows XP Access 2003
    Join Date
    Apr 2010
    Location
    Florida
    Posts
    6

    Network Database written in Access 2003 but unable to open with Access 2013


    I apologize if this subject has been covered in another thread but I couldn't find the same situation.
    We are running a network Access 2003 db. The only users with a full copy of Access 2003 on their PCs are the two Database administrators. All other users in the network have been opening it with Access 2003 Runtime. As PCs were replaced and Access 2007 & 2010 came standard with the Office packs, I was able to keep access to the db by making the newer versions unavailable (Control Panel>Programs>Change). But Friday I set up a new PC that came with Office 2013 and I cannot make Access 2013 unavailable so the User cannot access the 2003 db. I don't want to remove Access 2013 completely because we do need to upgrade to a newer version. But we are a small company and can't do it right now. I am concerned that if I convert a db for this user, then they won't get any of the changes made by other users or it will affect the other users access to the database.
    I have scoured the forum and internet and everyone's solution seems to be to convert it - either to a newer version of Access or SQL. Is there no other way to make this work?

  2. #2
    June7's Avatar
    June7 is offline VIP
    Windows 7 64bit Access 2010 32bit
    Join Date
    May 2011
    Location
    The Great Land
    Posts
    52,815
    Is this a split database?
    How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.

  3. #3
    JeanieMB is offline Novice
    Windows XP Access 2003
    Join Date
    Apr 2010
    Location
    Florida
    Posts
    6
    I am not sure what you mean.

  4. #4
    June7's Avatar
    June7 is offline VIP
    Windows 7 64bit Access 2010 32bit
    Join Date
    May 2011
    Location
    The Great Land
    Posts
    52,815
    Conventional practice when there are multiple users is to 'split' the db into front and back ends. BE has data tables, FE is the user interface. The BE can stay as an mdb file and the FE can be designed in whatever version you want so if you have to maintain two versions (2003 and 2013), both will be able to connect to the BE tables.

    Are you saying Access 2013 runtime won't open the 2003 db?
    How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.

  5. #5
    JeanieMB is offline Novice
    Windows XP Access 2003
    Join Date
    Apr 2010
    Location
    Florida
    Posts
    6
    I didn't try Access 2013 runtime because the PC came with full version of Access 2013 already installed. We have a programmer that setup the database but I run the run time installations on the computers in our network. What you are saying above about front end and back end sounds familiar but if you are keeping backends in two different versions, doesn't that mean that Users won't be accessing the same database and therefore won't be getting the same up-to-date information? I did try to open our database directly from Access 2013 but I received the error message about trying to open an older version & it wouldn't open up.

  6. #6
    June7's Avatar
    June7 is offline VIP
    Windows 7 64bit Access 2010 32bit
    Join Date
    May 2011
    Location
    The Great Land
    Posts
    52,815
    I am not suggesting two versions of the backend, only one. The frontend could be different versions, all connecting to the same backend file and therefore accessing the same data.

    I have not worked with Access 2013, don't want it.

    I have also never worked with runtime. Are you saying users all open the same file that resides on network server? I have done this with one simple db and so far it works but it is not the recommended approach with multiple users.
    How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.

  7. #7
    redbull's Avatar
    redbull is offline Competent Performer
    Windows XP Access 2003
    Join Date
    Mar 2012
    Location
    Missouri
    Posts
    480
    Quote Originally Posted by June7 View Post

    don't want it.
    Amen, However knowing my company.. it will be 2023 before I have to worry about it.

  8. #8
    JeanieMB is offline Novice
    Windows XP Access 2003
    Join Date
    Apr 2010
    Location
    Florida
    Posts
    6
    I checked with our programmer and he has heard of what you are talking about with an Access 2007 database and having Access 2007, 2010 or 2013 as the front end. However, our database is designed for multi-users at one time and our database is in Access 2003.

    Thanks for the suggestion though. It's beginning to sound like we will need to upgrade sooner rather than later.

  9. #9
    June7's Avatar
    June7 is offline VIP
    Windows 7 64bit Access 2010 32bit
    Join Date
    May 2011
    Location
    The Great Land
    Posts
    52,815
    The backend can remain an Access 2003 (mdb) file and the Access 2003/2007/2010 frontends will all be able to link to the mdb backend, I assume 2013 can as well. It is a workaround for mixed version users.
    How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.

  10. #10
    JeanieMB is offline Novice
    Windows XP Access 2003
    Join Date
    Apr 2010
    Location
    Florida
    Posts
    6
    We have Access 97/2000/2003 vintage workgroup-based security as part of the application and I know that workgroup based security disappeared with Access 2007 and newer. Would this be an issue trying to use a different program to access the database?

  11. #11
    June7's Avatar
    June7 is offline VIP
    Windows 7 64bit Access 2010 32bit
    Join Date
    May 2011
    Location
    The Great Land
    Posts
    52,815
    Maybe, I never used workgroup-based security and never dealt with any db set up with one, not even any posted to forum as far as I know. I don't know if splitting the db will resolve issue or open a new can of worms for users still running 2003 with workgroup security.
    How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.

  12. #12
    JeanieMB is offline Novice
    Windows XP Access 2003
    Join Date
    Apr 2010
    Location
    Florida
    Posts
    6
    Thanks very much for all of your input...it's sounding more and more like we will have no choice but to convert our database to a newer version.

  13. #13
    June7's Avatar
    June7 is offline VIP
    Windows 7 64bit Access 2010 32bit
    Join Date
    May 2011
    Location
    The Great Land
    Posts
    52,815
    Maybe just remove the workgroup feature from the 2003 db. How difficult would that be? Would that make the non-split db unworkable? I do have one extremely simple non-split db with multiple users and it seems to work even when more than one user at a time opens the same file but there is no code (macro nor VBA) in that db. However, as stated, this is not recommended for multi-user database.
    How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Access 2013 Database Name
    By Sparky in forum Access
    Replies: 2
    Last Post: 06-28-2013, 04:07 PM
  2. Replies: 2
    Last Post: 06-18-2013, 09:06 AM
  3. Replies: 1
    Last Post: 11-09-2011, 12:08 PM
  4. Unable to Read from COM ports in Access 2003
    By userThree in forum Programming
    Replies: 3
    Last Post: 07-31-2011, 08:59 PM
  5. Unable to open Access on Local Area Network
    By MikeWaring in forum Security
    Replies: 1
    Last Post: 12-24-2010, 11:46 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums