Why can't my Access file be opened?

[Vida]

You would normally find me in Mac DTP forums, so, I am a bit out of my element here. My company (publisher) puts content into various forms, and recently poured some course descriptions into Access for a client (to be put into content management system later, but to be viewed/revised in Access-not crunched). Our client can not open the sample file. It looks fine on our PC, and I have emailed it to 3 other PC people who have no trouble with the file. I don't think it is an email problem, becase they can open the Excell file sent at the same time.
They are running Windows 2000, Office 2000. File was created in Access 2000 (running Windows 98).
The error message "Unrecognized Data Base Format" even when trying to open from within Access. (I even tried sending it as Access 97, but that won't open, either.)
I really don't believe there is anything wrong with the file, but the client has tried it on several computers and can not open it.
I am baffled. I would appreciate any suggestions.

 

[KenReay]

Hi

Check version of Access your client using?

Access is not a standard part of all Office 'Packages' (certainly in UK). It is possible they are using Office 2000 but an older (Access95?) version of Access.

Hope this helps Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now -

http://www.kenneth.reay.btinternet.co.uk

UK

 

[Vida]

Thanks for helping.

I did check, and she insists she is using Access 2000. Any more ideas? I hate to lose a client over something like this :-(

 

[annsolomon]

You might suggest your client download the latest service packs for Windows and Office. Also make sure they have the latest version of Jet.

 

[Zeroanarchy]

Vida what was the Access file extension?? was it a MDB? or something else.

ZeroAnarchy
Experience is a wonderful thing. It enables you to recognize a mistake
when you make it again.

 

[Vida]

Good suggestion about the downloads. Can you briefly explain what Jet is? I'm already sounding like a moron to my client, I'm afraid.

Yes, the extension is .mdb. (Zero- I love your tagline.)

 

[annsolomon]

I know what you mean about sounding like a moron to your client. It's sooooo hard to troubleshoot from afar; you have you take their word without knowing their experience level.

I certainly don't pretend to be an expert. (These forums are great 'cause we can share what we know even if we don't know everything about everything.) If this insults your intelligence or experience it's definitely not intended because I'm still trying to get a handle on this myself. Access isn't exactly a database; it's a database client. Jet is the actual database (kinda like SQL Server). You can download the latest version of Jet from the Microsoft website.

Please, ANYBODY out there who can explain this better, jump in.

 

[frozedog]

PRB: Error "Unrecognized Database Format" When You Upgrade to Access 2000 or 2002
The information in this article applies to:
Microsoft Visual Basic Professional Edition for Windows 5.0
Microsoft Visual Basic Professional Edition for Windows 6.0
Microsoft Visual Basic Enterprise Edition for Windows 5.0
Microsoft Visual Basic Enterprise Edition for Windows 6.0
Microsoft Access 2000
Microsoft Access 2002
Microsoft Data Access Components 2.5
Microsoft Data Access Components 2.6

This article was previously published under Q238401
SYMPTOMS
If you try to gain access to an Access 2000 or Access 2002 database, you may receive one of the following errors within your Visual Basic program.

If you are using Microsoft ActiveX Data Objects (ADO) (or the ADO Data Control), you receive the following error message:

Run-time error -2147467259 Unrecognized Database Format XXX
If you are using Data Access Objects (DAO) (or the DAO generic Data Control), you receive the following error message:

Run-time error 3343 Unrecognized Database Format XXX
CAUSE
Access 2000 and Access 2002 use the Jet 4.0 engine, which creates Jet 4.0 format database files. Jet 3.5 components do not recognize such a format.
If you are using ADO, you get error -2147467259 when you try to connect to your Access 2000 or 2002 database through the Microsoft.Jet.OLEDB.3.51 provider.
If you are using DAO, you get error 3343 when you use the Microsoft DAO 3.51 Object Library.
The DAO generic Data Control does not work against Access 2000 or 2002 databases and always generates error 3343 unless it is used as instructed in the "Resolution" section of this article. This occurs because this control is based on Jet 3.51 and only recognizes Jet 3.51 (or before) database formats.
RESOLUTION
To resolve this problem, use one of the following methods:
Install Visual Studio Service Pack 4 or later. (If you are using the Data Control, change its Connect property to Access 2000.)
For ADO (or the ADO Data Control), use the Microsoft.Jet.OLEDB.4.0 provider.
For DAO, add a reference to the Microsoft DAO 3.6 Object Library.
If you use the generic Data Control, you must open a DAO 3.6 recordset and then assign it to be the source of the Data Control as follows:
Option Explicit
Private daoDB36 As Database
Private rs As DAO.Recordset
Dim sPath As String

Private Sub Form_Load()
sPath = _
"C:\Program Files\Microsoft Office\Office\Samples\Northwind.mdb"
Set daoDB36 = DBEngine(0).OpenDatabase(sPath)
Set rs = daoDB36.OpenRecordset("Customers&quot
Set Data1.Recordset = rs
End Sub

This problem has been addressed by Visual Basic Service Pack 4. A new value (Access 2000) has been added for the Connect property that will allow the DAO Data Control to open Access 2000 databases.
STATUS
This problem was first corrected in Visual Studio 6.0 Service Pack Service Pack 4.For additional information about Visual Studio service packs, click the following article numbers to view the articles in the Microsoft Knowledge Base:

194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why

194295 HOWTO: Tell That a Visual Studio Service Pack Is Installed

To download the latest Visual Studio service pack, visit the following Microsoft Web site:

http://msdn.microsoft.com/vstudio/downloads/updates.asp

REFERENCES
For more information on Jet 4.0, refer to the Access 2000 documentation.

For more information on ADO and DAO, refer to the Visual Basic documentation.

For more information, query on "Unrecognized Database Format" in the MSDN Library that is supplied with Visual Basic.

 

[Vida]

Thank you, ann, that helps, actually.

You also hit on an important issue about doing this from afar, and not knowing how much our client really knows, or is pretending to know. None of our publishing/html clients are local, nor the printers, for that matter. Magic of digital prepress. Ordinarily, it isn't a problem. But my troubleshooting talents may be limited to programs I am familiar with.

So, I will pass those suggestions along.

My boss had the idea to find a MS Tech near the client, which I did. I sent a CD of the file, and will find out 'officially' if there is a problem with the file. But I would still appreciate any ideas you folks have.

 

[annsolomon]

frozedog, help out an old lady. Can you pinpoint the parts in your post that are specific to his issue or, at least, not specific to Visual Studio? I'm home SICK today so the brain's not working well.
Thanks.
Ann

 

[annsolomon]

Vida, kudos to your boss! You never know what resources a company has. But, "hands on" is always better in my book. Good luck. I'd like to know how this turns out for you.
Ann

 

[Vida]

I must have ben in a timewarp; saw ann's but not frozedog's reply earlier. Apologies. I am a little overwhelmed by the info, but I think I see where it is going. Will print it and meditate on it, and have more things for my client to try.

Though I am hoping the rentageek solves this for me

Ann, I will post what happens. Thanks for your help, and your interest in my little problem. I hope you feel better, as well.

 

[Hunter1]

Just a thought, however, I have had a similar problem with Access files copied to CD. Have the client check the properties of the file.

Open Windows Explorer, find the file and then right click the mouse on the file name. Check to make sure the file is not marked as read only.

 

[Vida]

I did ask about properties, already. We have been working on this a few days, and tried some stuff, including that.

As for Read only, shouldn't they still be able to open the file? (I've had problems with files copied from CDs, but I could look at the files. Had to rename them or something to work in them. Though they were not Access files.) Plus, they had the same problem when I emailed the test file.

Partial update: the MS guruforhire confirms my file is fine, and should be able to be opened by anyone running Access 2000. Armed with that, I will confidently request to work with someone from IT (this is a University) instead of directly with the client. Wish me luck!

 

[Zeroanarchy]

Ok you will find that if you have split the database and the backend is readonly you will not get access to the program, it will come up with the readonly message and most likely hang after that.

If you only have one table perhaps an other alternative is to export the data to an excel file and have the client view the data through excel.

Ok as for what frozendog said here is how to check to see what version of ADO or DAO you are using.

Step 1. Goto a form (any form you have or have not created)
Step 2. Select View from the top menu
Step 3. Select Code
Ok this should show you the VB code behind your form
Step 4. Select Tools from the top menu
Step 5. Select references
Ok the refrence box should be visable as you can see your program uses a list of ouside refrences to run your Access database, each refrence has a file attached to it in the computer system somewhere.

Your list should have the following ticked off:
Visual Basic For Applications
Microsoft Access 9.0 object Library
OLE Automation
Microsoft ActiveX Data object 2.1 Library

What you need to do is make sure that all the files that these refrences are connected to are availble on your clients machine and that they are at the same address as they are in your list other wise you are likely to get an error.

Hope this gives you a bit of direction.
ZeroAnarchy
Experience is a wonderful thing. It enables you to recognize a mistake
when you make it again.

 

[Vida]

Thanks, Zero! That is superhelpful.

BTW, we did make an Excell version, and she can open that. But it isn't as nice for presentation. (Please don't roll your eyes.)

I think we are on track.

 

[Vida]

Partial update, for those who were so kind as to give me advice: My boss called my contact's boss. He can open the file on his laptop (hahaha). He will arrange to have the IT staff contact us. The big plus is, I think we will get the job!

Meanwhile, we found the situation at many Universities is that they get one or two disks, and 900 licenses. So, all the puters will be configured the same. We also think the problem is either 1. the thing you described about the packets not being updated, or 2. some kind of system-wide virus protection.

So, thanks!