Convert Access 2000 MDW-file to later version

[AdriGenis]

I have an Access application started in Access 2000. The Workgroup file was created in Access 2000. It worked fine in Access 2007, but when I try to use it in Access 2013 (or later) it says that it cannot open a file in a older/previous version format.

I know I have to convert it from the older format. I have installed Access 2003 (on a virtual machine), and opened the Workgroup file with a copy of it as the Workgroup file. I don't seem to get the correct user with the necessary rights. I suspect that the original developer has created another user (SysAdmin) with the correct rights.

Does anybody have any advice?

[NeoPa]

I'm confused. If you have the same MDW file as you had before then it should behave in the same way. Are you still using the original MDW file?

[AdriGenis]

I want to convert it (the MDW-file) from Access 2000- to 2003+-format. When I use normal Access 2003 (double click on it), it offers to convert the old format, but doesn't have access to the MSysObjects and MSysACEs (system) tables. If I use the same MDW-file (specified on the command line) and open a copy of the MDW-file, I get a message that the user with admin-rights doesn't have the rights to open the file.

[NeoPa]

MDW files are not designed to be opened in Access as an ordinary database. They are opened automatically as part of the process of opening MDB/E databases (NOT AccDB/E ones).

I'm not aware that the format of the MDW file ever changed either. Why are you trying to change what I guess would be a perfectly workable MDW file?

NB. Please do try to give a direct answer to any questions posed. Our expertise is reflected in the questions we ask. If you respond with an explanation but no direct answer then we're limited in how much we can help.

[AdriGenis]

It is quite simple - I have a .ACCDE front-end and .MDB back-end (with user level security). When I try to run this on Access 2016 (Office 365), I get the following error:
Cannot open a database created with a previous version of your application.
see https://bit.ly/2MzlLDv
I can (obviously) open the FE, as well as the BE-files on their own. So it seems as if the problem lies with the MDW-file?

[NeoPa]

AdriGenis:
It is quite simple

I doubt you'd be here asking for help if that were true. Let's try to avoid jumping to unwarranted conclusions. They typically lead us astray.

So, we have a very complex scenario here. One that's very rarely used I'd guess (though I doubt it's that rare as it makes sense at a very basic level). Where you're usage is different is that it seems you have an MDW file that's in use for your MDB version of Access - but not the one in use for Access 2016 - if there even is one (I expect there is one still, under the hood).

Now, if you want to use the MDB file that has MDW restricted access then you'll need to open Access with the /wrkgrp parameter set specifically to the MDW file used for your MDB file. I hope that makes sense.

I did check that Access 2016 still supports that parameter and perhaps it doesn't, which is a real problem if true. I did check Command-line switches for Microsoft Office products and selected Access and it wasn't listed, but it says it's not a definitive list so I suggest you try it and see. As AccDBs can still link to MDBs then it would seem important to continue to support this avenue.

Let me know if this turns out to be a limitation and I'll put an email together for the Access team to look into at Microsoft. They, or one of the other Access MVPs, may know a way around it that I don't. It's not something I work with much nowadays though I did play with MDW security back in the day.