Access 2010 dislikes my .mdb file - ms-access

I apologize for this amateur question: this is my first experience with MSaccess.
When I try to start access 2010 by double-clicking my client's custdb.mdb, access 2010 complains:
Unrecognized database format 'custdb.mdb'
My client says only that "yeah, access 2010 is a problem."
Has anyone any idea what the problem might be and how I can fix it?
Alternatively, can anyone point me to a spot where I can download an earlier version of access, like maybe access2007. The MS download page insists I download Access2010.
Thanks!

I've always used MDB viewer for this purpose (http://www.alexnolan.net/software/mdb_viewer_plus.htm)
I then copy the data from that into MS Access 2010. It's a pretty horrible solution but it was the best I could come up with at the time!

This is probably a Jet 3 database. You can see that by opening the file with a hex viewer. Access 2010 doesn't handle Jet 3.

Related

Microsoft CommonDialog Control for higher version of MS Access

I've been searching the web for answers but got no success to find the right thing to do. So this is my last resort.
We have an Access database (1997) and works perfectly in our old remote server. But when we migrated it to Windows 2012 Server and convert it to .accdb file format, the CommonDialog built-in method which opens a window for selecting a file is not working and error message pops up.
By that we are completely aware that some references are missing and we were right.
We searched the web and realized that we need to use the Application.FileDialog under Microsoft Office x.0 Object Library for higher version of MS Access. We implemented that for some of our VBA code that utilizes the CommonDialog and it worked.
But we are also thinking on how are we able to continue using the CommonDialog for higher version of Access just for the sake of not tweaking our VBA code?
If you have an idea about this, I would be glad to hear. Thanks in advance!

Can we run Access macro without MS Access?

I have created .mdb (Access macro) for client but problem is that they are migrating to Office365 so access will no be longer available for them.
Can I run Access macro without MS Access? I have googled it, I found .MDE file can solve the problem, but I don't have idea about it. Is there any alternative option or .MDE file will be the solution?
I'm a beginner in Access please let me know if any suggestions are available.
Thanks in advance!
You can't.
But Access is indeed available through O365 - you just have to select and pay for the correct subscription.
Microsoft just recently changed the Office 365 subscriptions. Microsoft Access is now included in all of the subscription levels except the Business Essentials subscription.
If users of your Access application have no license for Microsoft Access they still can use the Microsoft Access Runtime. The Access runtime is available for download free of charge and can run Access Database Applications, but you cannot make any design changes in it.

View a replicated Access 2000 database in Access 2016

I've an old replicated Access 2000 database. I want to get to the code and some of the forms as I'd like to revive parts of it, and also see how I dealt with things back then.
I have the Access 2000 CD, but it was an upgrade from Access 97 and the Access 97 CD is too damaged now to load. Access 2016, which I have now, won't open replicated databases.
Is there any way I can open or convert the .mdb file? I only need to view it in design mode.
You'll need Access 2010 or lower to open it.
If the database doesn't contain confidential data, you could upload it to a file hoster and some good soul might convert it for you.
If it does, you will have to go scouting for a used copy of an old version, I'm afraid.

MS Access Converting from Run Time to accdb?

I was wondering if it was possible to convert a 2007 MS access runtime database (The one where you have to click the setup and install it) back to an accdb? I just want to do this as a way to back it up.
Thanks in advance!
I figured it out! You just have to rename the accdr back to accdb.

Viewing ACCDB with Access 2010 runtime when Access 2007 is installed

I'm hoping someone can either tell me what I'm doing wrong correct my flawed understanding of how this works and explain why it's not possible.
I've been developing a fairly basic database/program for a client in Access. They have Office 2007, I have Office 2010. Initial test of creating a database in 2010 (in "2007" format) and opening the forms and data in Office 2007 showed no problems.
Fast forward 3 weeks. I've sent them a recent copy for approval and they can't open it. Unrecognised database format. Upon looking around, it seems Access 2007 format doesn't really mean anything in terms of backward compatibility (thanks M$). I COULD follow the seemingly standard answer and remove empty fields, calculated columns etc but really don't think it should be necessary.
I've installed the Access 2010 runtime on one of the target systems with the understanding that it would allow me to open the Access 2010-developed ACCBD. No luck. Office 2007 still launches, and "unrecognised database format".
Is the problem that Access 2007 is installed on the target system? Or am I perhaps misunderstanding what the Access runtime distribution is for? Basically, is there a way to still deploy a program/database developed in Access 2010 without a) installing (and purchasing about 60 licenses of) Office 2007, or b) stripping back the existing ACCDB.
I haven't worked enough with A2007 and A2010 to help with the problem of A2007 not being able to open the ACCDB in which you were working in with A2010. Your understanding of how the Access runtime is for is basically correct.
However when the client was executing the A2010 runtime against your ACCDB did they create a shortcut referencing the path to the A2010 runtime msaccess.exe and the path and file name of the ACCDB? Similar to
"C:\Program Files\Microsoft Office\OFFICE14\ART\MSACCESS.EXE" "Q:\1 access\NewsgroupAnswers.mdb"
You can save in 2007 format from 2010 but one little known issue is that when you make changes in a 2007 access file within 2010 you will not be able to open it in 2007 again. To fix this you must create a -new- 2007 file and import all items into the fresh one (just compact and repair will not work) and then this new file should be usable within 2007 once more.