.accdr file issue

[ItsMe]

I tried several things, including publishing as accde and then trying to open as accdr and back to accdb. I tried all types of combinations to try and recreate the error you are getting. I used machines with Runtime and Full versions of Access. I even used a machine without Access and renamed the extension to see if I could get the file to break. There was only one way I could get that error message.



The only way I could get that message was to use a machine that has an earlier version of Access, 2003. Using an incompatible version did the trick. But this does not add up if the file was orignally working with 2007 and now you can not open it with 2007.

Either the file is corrupt or we are trying the wrong extension. Hopefuly you have made a few copies already. Look at the file sizes and modification dates for the files. Grab one that looks normal and give it an mdb file extension. If that does not work….

Create a new, blank DB. Rename one of your copies to ACCDB. From the New Blank DB use the External Data Tab to try and Import the objects from the file that you named with the ACCDB file extension. You will not be able to import objects from a file with accdr or accde.

If that does not work I do not know what to suggest other than try to open it with a full version of Access 2010. But not being able to open it with RT 2010 would indicate it work anyway. I have, in the past, been able to break files by opening the same file with different versions of Access, over a network, in rapid succession of opening and closing. I do not believe I got the extension warning you see but do not remember exactly.

Post what you find trying my suggestions.

[EdCanada]

I tried to rename it with .mdb and this didn't work, I got unrecognized file extension.
I tried the blank database by importing after renaming from accdr to accdb and I got unrecognized extension.
I installed Access 2013 full version of access and still the same problem, unrecognized extension.

I installed a Access Runtime 2010 on a different computer and I got different error message saying the Visual Basic required.

I don't know what to do.

Do you know how to use the Runtime Command Line? They are saying that I can change the extension using the command line. The accdr cannot be renamed by right click and rename.

[ItsMe]

Not familiar with Runtime Command Line. The statement, by itself, sounds like an oxymoron to me. There are switches that you can use at startup via the command line. I have only used switches like compact and backup.

I could probably look into it and write up a line that you could paste into your RUN window.

Answer these questions for me, please.

Who mentioned the Command Line?
Do you have a copy of the DB that will open on a computer, any computer?
Can you identify a copy of the file that is closest to the original at the time it first threw the error?
If you were to use a command line switch,
what operating system would be on the computer?
what version of access would it be (full version)?

[EdCanada]

Who mentioned the Command Line?
Google. I was looking for the error message online and I found some people used the command line to convert the accdr files.

Do you have a copy of the DB that will open on a computer, any computer?
I didn't understand the question. All we use is the .accdr file and this is our database. Other users can open a different system that we have also based on access accdr file extension and there are no issues with that system.

Can you identify a copy of the file that is closest to the original at the time it first threw the error?
This is the only file that we have.

If you were to use a command line switch,
what operating system would be on the computer?

Windows 7.
what version of access would it be (full version)?

I have Access 2007 and I have also Access 2013 on another computer.

Thank you for taking the time to help, I really appreciate it.

[ItsMe]

There is no conversion of accdr files to accdb. You can rename the extension. One of the first tests I did last night was to see if I could break an accdb file by using a computer that did not have access installed and renamed the extension. It did not break. I did the same on a computer with the wrong version of access. It did not break. I have been able to, in the past, break files by accessing the same accdb file from different computers using different versions of access. That is likely what happened to your file.

I looked into switches and I can not find any that mention renaming the extension. I could do it VIA MSDOS but I do not see the reasoning plus, I would have to dig to find my notes. I could rename the extension using VB Script, which will do the same; use Windows Shell to rename the file. I am not convinced this approach is different from using the GUI and clicking the file to rename it.

Assuming W7 64bit and Access 2007 32bit, here is a switch that will run a repair but it will probably not work because of the fact the file will not open.

C:\Program Files (x86)\Microsoft Office\Office12\MSACCESS.EXE "C:\FolderName\FileName.accdb" /repair

The only other thing I can suggest is zip down a copy of your file and email it to me to see if I can help.

[amrut]

ItsMe is already helping you out. A want to add few bits. While reading through, I was unable to decide whether the file is a compiled (accde renamed to accdr ) or an editable accdb (accdb renamed to accdr). If one form is ( as mentioned in one of your posts) culprit, try to find it using an utility called Properties Setter Acc 2010. Using this utility, you can also get into the database by setting desired properties. If it is an accde file, you can change the first form to open if it is not switchboard or required for navigation else ...

Post # 7 : I think an access 2007 db file once opened and saved in Access 2010 cannot be reopened in 2007. I have faced this problem sometime back.

Post # 10 : The error is due to the lower version of the file called VBE7.dll on the target machine than development machine. I have faced this while deploying to a Access2010 runtime only machine as it had a lower version of this file than development machine. See https://www.accessforums.net/access/...ons-40777.html

Best of luck.