Share via

Converting Access 2003 database to 2016 format

Anonymous
2018-06-16T15:51:24+00:00

Dear,

Our database was constructed in Access 2003 format with security permissions for users. I want to investigate what would happen if we upgrade the database format to 2016. But I have only one computer to do this and I don't want to do an upgrade that will make an impact on our current database because our whole organisation is using it all the time. I have a copy of the database on a local machine which shouldn't make a difference for the live database that is on the server.

I apologise for this very green and basic question but should I be all right to do a conversion of the local copy of the database to the newer format? And still be able to access the live database in its format if I need to? And without impact to my colleagues use of the database?

Thanks,

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

  1. Anonymous
    2018-06-16T17:36:34+00:00

    The local copy of your FE and BE should be converted, but of course you should NOT convert your "live" copy.

    You can convert that local copy without impacting your other users. Just be certain to do as Daniel instructs, and work ONLY on that copy you have on your local machine.

    1 person found this answer helpful.
    0 comments

Answer accepted by question author

  1. Anonymous
    2018-06-16T16:12:37+00:00

    You should be able to proceed in that manner, but i wouldn't.

    I'd copy the front end and back end locally, relink the front end to your local back end.  This way you have an isolated development copy.  Now so your upgrades, tests, ... And then, when you are ready, you can relink it to the server backend and distribute the upgraded frontend.

    Do note that user security was dropped long ago, so you'll need to implement your own.

    1 person found this answer helpful.
    0 comments

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-06-19T12:22:55+00:00

    If you use ULS, then both the FE and BE must be secured with the same workgroup file, so you could not convert one only - you'd have to convert both.

    0 comments
  2. Anonymous
    2018-06-19T04:48:27+00:00

    Thanks for your help.

    I realize now that there were more problems involved when converting it. My main concern, I think, was the fact that it has User-Level-Security, and I will need to find a way to remove that. Or maybe I can just create a new frontend that connects to the old format. But this moves the question to other areas. Thanks for your replies and it looks like it is working as you say.

    0 comments
  3. Anonymous
    2018-06-16T16:25:31+00:00

    Ok, yes, I think that is what I meant and plan to do.

    I have a local copy of both front end and back end which I was planning to convert. But I might still need to open the other front end that is linked to the back end on the server. In my mind it should be possible but wanted to ask others opinion or advice.

    Or did I misunderstand and that you think I need to keep it separate until the new frontend is developed?

    Thanks,

    0 comments