SOLVED

Will Access 2019 Run an Acess 2000 mdb?

%3CLINGO-SUB%20id%3D%22lingo-sub-3190382%22%20slang%3D%22en-US%22%3EWill%20Access%202019%20Run%20an%20Acess%202000%20mdb%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3190382%22%20slang%3D%22en-US%22%3E%3CP%3EI%20use%20Office%202010%2C%20which%20I've%20had%20to%20re-install%20after%20a%20reformat.%20Unfortunately%20I%20guess%20Microsoft%20doesn't%20support%20Office%202010%20anymore%2C%20so%20none%20of%20the%20bugs%20in%20my%20copy%20have%20been%20updated%2C%20and%20therefore%20Outlook%20and%20the%20other%20apps%20keep%20freezing%20with%20no%20readily%20apparent%20way%20to%20resolve%20this%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20considering%20upgrading%20to%20Office%202019%20Pro%2C%20but%20.%20.%20.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20written%20a%20number%20of%20VERY%20COMPLEX%20Access%202000%20split%20databases%20over%20the%20years.%20When%20I%20say%20complex%2C%20I%20mean%20mega%20thousands%20of%20lines%20of%20Access%20VBA%20code.%20When%20I%20tried%20to%20convert%20one%20of%20my%20databases%20to%20accdb%20format%2C%20it%20left%20me%20with%20hundreds%20of%20errors%20in%20my%20code.%20Therefore%2C%20converting%20my%20databases%20is%20not%20something%20that%20I%20can%20consider.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20for%20the%20%2464%20question%3A%20Will%20Access%202019%20reliably%20run%20an%20Access%202000%20mdb%3F%20I've%20searched%20the%20web%20and%20can't%20seem%20to%20find%20a%20decisive%20answer%20to%20this%20question.%20If%20it%20will%20run%20an%20old%20mdb%2C%20Is%20there%20anything%20else%20I%20should%20know%20before%20spending%20the%20money%20to%20buy%20Office%202019%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3190382%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Eaccess%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3190570%22%20slang%3D%22en-US%22%3ERe%3A%20Will%20Access%202019%20Run%20an%20Acess%202000%20mdb%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3190570%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1312983%22%20target%3D%22_blank%22%3E%40Neuro-VISION%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Foffice%2Fwhich-access-file-format-should-i-use-012d9ab3-d14c-479e-b617-be66f9070b41%23__toc306205042%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3ESomewhat%20surprisingly%2C%20it%20sounds%20like%20it%20might%20be%20possible.%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20page%20says%2C%20in%20part%2C%3C%2FP%3E%3CH2%20id%3D%22toc-hId-366857689%22%20id%3D%22toc-hId-366855834%22%20id%3D%22toc-hId-366855834%22%20id%3D%22toc-hId-366855834%22%3EThe%20.mdb%20file%20formats%3C%2FH2%3E%3CP%3EBefore%20the%20.accdb%20file%20format%20was%20introduced%20in%20Access%202007%2C%20Access%20file%20formats%20used%20the%20.mdb%20file%20extension.%20There%20are%20multiple%20different%20versions%20of%20the%20.mdb%20file%20format.%3C%2FP%3E%3CP%3EYou%20can%20still%20open%20some%20.mdb%20files.%3CSTRONG%3E%3CEM%3E%20If%20the%20file%20is%20stored%20in%20the%20Access%202002-2003%20or%20Access%202000%20file%20format%2C%20you%20can%20open%20it%20and%20use%20it%20normally.%3C%2FEM%3E%3C%2FSTRONG%3E%20However%2C%20you%20cannot%20take%20advantage%20of%20features%20that%20require%20the%20.accdb%20file%20format.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3190575%22%20slang%3D%22en-US%22%3ERe%3A%20Will%20Access%202019%20Run%20an%20Acess%202000%20mdb%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3190575%22%20slang%3D%22en-US%22%3EThank%20you%20so%20much%20George.%20I%20have%20no%20need%20for%20any%20advanced%20features%20or%20replication%2C%20so%20running%20my%20databases%20under%20Office%202019%20Pro%20looks%20like%20an%20easy%20out%20of%20my%20Office%202010%20freezing%20problems.%3C%2FLINGO-BODY%3E
Occasional Contributor

I use Office 2010, which I've had to re-install after a reformat. Unfortunately I guess Microsoft doesn't support Office 2010 anymore, so none of the bugs in my copy have been updated, and therefore Outlook and the other apps keep freezing with no readily apparent way to resolve this issue.

 

I'm considering upgrading to Office 2019 Pro, but . . .

 

I've written a number of VERY COMPLEX Access 2000 split databases over the years. When I say complex, I mean mega thousands of lines of Access VBA code. When I tried to convert one of my databases to accdb format, it left me with hundreds of errors in my code. Therefore, converting my databases is not something that I can consider.

 

Now for the $64 question: Will Access 2019 reliably run an Access 2000 mdb? I've searched the web and can't seem to find a decisive answer to this question. If it will run an old mdb, Is there anything else I should know before spending the money to buy Office 2019?

10 Replies

@Neuro-VISION 

Somewhat surprisingly, it sounds like it might be possible.

 

That page says, in part,

The .mdb file formats

Before the .accdb file format was introduced in Access 2007, Access file formats used the .mdb file extension. There are multiple different versions of the .mdb file format.

You can still open some .mdb files. If the file is stored in the Access 2002-2003 or Access 2000 file format, you can open it and use it normally. However, you cannot take advantage of features that require the .accdb file format.

Thank you so much George. I have no need for any advanced features or replication, so running my databases under Office 2019 Pro looks like an easy out of my Office 2010 freezing problems.
best response confirmed by Neuro-VISION (Occasional Contributor)
Solution
My lack of naivete prevents me from saying flat out "it'll work", but that page is reassuring nonetheless. Having been around long enough, I will believe it completely when you report success.

@Neuro-VISION

It OUGHT to be OK :~>

 

All versions of Access can still open files created in Access 2000 or later.

In fact, they can also still save files in Access 2000 or 2002/2203 format.

 

However, I would still recommend converting your files to ACCDB format as the newer file format is more secure. 

Access 2019 and 2010 share the same file format so upgrading shouldn't cause any new issues in theory.

Of course, there are caveats e.g. where features that were in the earlier version have since been deprecated e.g. user level security dropped with ACCDB format, pivot tables deprecated in 2013 etc.

Also newer versions of Access are less tolerant of 'sloppy' coding. Things that compiled in A2000 may no longer do so in some cases

 

Good luck

Thanks for your reply and advice. But as I stated in my original post, I already tried converting to an accdb, and got hundreds of problems in my VBA code. Man others have posted that this is par for the course. I have no intention of spending a couple of hundred hours fixing bugs created by conversion. This is only one of the complex databases that I've developed over the years and still use, and it has many thousands of lines of VBA.

@Neuro-VISION 

It is true that later versions of Access are far less tolerant of ambiguities in code, and that, moreover, there are often improved ways to accomplish things. 

 

For example, at one time a statement like this was quite acceptable in Access VBA.

 

Public Function DoThis()

    Dim db as Database

    ---do something with db

End Function

 

In more recent versions, one would probably need to qualify that more carefully and explicitly.

 

Public Function DoThis()

    Dim db as DAO.Database

    ---do something with db

End Function

 

 

The same is true of a number of other coding practices. Greater explicitness is more likely to compile and run cleanly.

 

In the end, though, as long as the existing solution meets your needs, that's what matters.

Thanks for that advice! I've been coding since Access 97 was popular, and I'm usually very explicit in my code. But there is always the possibility that I've been sloppy here or there, and this is good advice.

I'm going to buy Office 2019 and see how it goes. So I may be back for more advice.

Well, I bought 32 bit Office 2019 and the A2000 MDB format seems to work okay! All of mine decompiled the first time I ran them, but that is no big deal. I haven't run them much yet, so I can't swear that everything works, but it looks good.

I also took the time to figure out why my MDB's weren't converting well to accdb's. Access 2019 actually does the conversion quite well. What it doesn't do well is to retain the references to the dlls, ocx's - library files. So refer back to the unconverted MDB so that you can see where each one is stored on your harddrive, and reset them after you've converted to accdb!

One last note: If you've written your db to run under 32 bit Access, unless you really want to do a lot of recoding, stay away from Office / Access 2021. It appears that it is only available for 64 bit, and you will NOT be happy when you try to run your 32 bit code AT ALL! I am speaking from experience.

I bought Office 2021 and luckily the vendor allowed me remove it and gave me a license for the 32 bit version of Office 2019.

 

SPOILER ALERT: Apparently there is a 32 bit version of Office 2021, but for some reason the vendor I purchased from did not offer that download.

@Neuro-VISION 
First, congratulations on the progress.


Apparently the first time you purchased the 64 bit version of Access for 2019. That is now more or less the default, but you CAN still obtain and use the 32 bit version, as you learned. I don't know which vendor you purchased from, but it seems they'd be aware of the situation and offer you a choice at purchase, although they did step up later.

 

For a long time, 32 bit was still being offered as the default although 64 bit Access has been available for quite a well. Today, 64 bit Office is the default. Unfortunately, one has to be aware of the issue in order to make an informed choice at the time of initial installation. 

 

All of that said, it is possible to convert your 32 bit Access accdbs to run properly under 64 bit Access. There are a lot of resources to help you with that in your VBA. In particular, I'm aware of at least 3 or 4 very good YouTube videos. Look for them under 32 bit vs 64 bit or similar terms. Colin Riddington (isladogs), who posted above, has at least one, for example.

 

However, many third-party OCX's and DLL's do not offer 64 bit versions of their tools, so it's not always possible to simply replace them. In some cases, you'll simply have to find another alternative that will run under 64 bit Access.

 

I guess in summary I'd say for the time being it's appropriate to stick with 32 bit Office but you should probably plan for shifting to 64 bit at some point.

Thanks George!