Unrecognized database format
Heisl...@gmail.com
getting an "unrecognized database format" error.
The database was created in Access 2003. I'm trying to open it with
Access 2003. The client can open it on her computer with no problem,
and she was able to compact and repair it, and resend it with no
problem. Yet I still get the error.
If the database is corrupt, I would suspect that she'd be getting
errors on her end, too, but she's not. Nonetheless, I'm going to ask
her import all of the objects into a new database and resend.
Other than corruption, what else could contribute to this error? It's
not a version issue.
Kurt
Heisl...@gmail.com
resend - I'm still getting the same error when I try to open it.
The only version difference we have is she created the database in
Access 2003 SP1, and I'm trying to open it in Access 2003 SP2. But
this has never caused a problem.
Confused.
'69 Camaro
> Update: I had her import all the objects into a new database and
> resend - I'm still getting the same error when I try to open it.
Does the file have, or did it ever have, a digital signature? Does the file
have, or did it ever have a VBA password assigned? If the answer is yes to
either question, then have her create a new Access 2000 database format
database and import all of the objects into it, then compile the code and
compact it. Have her zip the file and send it to you, without adding a
digital signature or VBA password. When you receive the file, scan the file
with your up-to-date antivirus software to determine whether or not it
contains any viruses. If it doesn't contain any viruses, unzip the file,
set your Macro Security setting to low (if it isn't already) and attempt to
open the database file.
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
Heisl...@gmail.com
But I think I found the problem - the user sent the database to me via
an online file transfer "sendit" link designed to transfer large
files. (A legitimate one that our organization hosts.) It seems that
databases sent through this link produce the error on the receiving
end.
But the error doesn't occur every time. I had some other people send
me some databases with the sendit link, and I got the error when I
tried to open the database. They got the error if I sent a database to
them. But if I send a database to myself through the send it link, no
error. Very weird.
The file transfer thing shouldn't cause this problem, because with the
link you simply upload a file (any kind up to 75 MB), put in the email
address, and click send.
Very strage!
On Jun 18, 2:23 pm, "'69 Camaro" <ForwardZERO_SPAM.To.
69Cam...@Spameater.orgZERO_SPAM> wrote:
> Hi.
>
> > Update: I had her import all the objects into a new database and
> > resend - I'm still getting the same error when I try to open it.
>
> Does the file have, or did it ever have, a digital signature? Does the file
> have, or did it ever have a VBA password assigned? If the answer is yes to
> either question, then have her create a new Access 2000 database format
> database and import all of the objects into it, then compile the code and
> compact it. Have her zip the file and send it to you, without adding a
> digital signature or VBA password. When you receive the file, scan the file
> with your up-to-date antivirus software to determine whether or not it
> contains any viruses. If it doesn't contain any viruses, unzip the file,
> set your Macro Security setting to low (if it isn't already) and attempt to
> open the database file.
>
> HTH.
> Gunny
>
> Seehttp://www.QBuilt.comfor all your database needs.
> Seehttp://www.Access.QBuilt.comfor Microsoft Access tips and tutorials.
'69 Camaro
> But I think I found the problem - the user sent the database to me via
> an online file transfer "sendit" link designed to transfer large
> files.
Ah. That can happen when FTP transfers between different OS platforms are
made and the default Windows setting is used. Ensure that it's a binary
transfer when uploaded and a binary transfer when downloaded, not "default"
and not "ASCII," either.