Discussion Locked

VB error 3343 unrecognized d'base format

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

An error was reported to me two days ago regarding an Access application that we developed for 15 network users.

The error occurs in a VB and generates error number 3343 unrecognized database format.

A visit to microsoft's web site shows the error documented. However, after reviewing the documentation and the site we see that everything is up to date, per the Q article.

No new apps have been installed across these 15 machines. The only thing that has changed is ip address assignmentwas moved from static to dhcp. Any suggestions ?

OS - WINNT WKS, WIN98, WIN2K
SERVER - WINNT - SVC PK 6
OFFICE SR-1

TIA -

8 replies

by sl-campbell

Still missing some info here:
Is the database an MDB?
What version is the database if it is a MDB, (97 or 2000)?
What version is Access, (97 or 2000)?

Is the app using ADO or DAO and if so, what version?

Have you done a repair and compact on the database if it is an MDB?

by sl-campbell

Is it possible that the MDB is in 2000 format, but the VB application is trying to access the MDB with an older DAO version?
Can you open the MDB with access? If so, which version?

Also, do you have the correct MDAC update?

Like I said above, need more info. But first do a repair on the MDB.

by dsa

You need to isolate the problem. Here are the steps that you should do:

1. Make a backup of your all your data mdb's. Hopefully, the data is separated from the programs.
2. Run the Repair Mdb. The usual cause is that there was a bookmark created on one of your data tables. Usually this will solve the problem.

If the above does not solve your problem, then check the following to isolate the problem:

1. Is this happening on all 15 machines?
2. If yes, it is most likely you have a corrupted table common to all 15 users. If No, find out which table is corrupted that is being used by the machines that are giving the error number.
3. Run the same program using known good database from backup. This will tell you whether it is the program or the data.

4. If it is data, then isolate the tables one at a time until you find the corrupted table.

5. If it is the program, then you create a new program.mdb and import all the tables, queries, forms, macro and modules. It will not import the corrupted form or modules.

6. Upgrade to SR-2. This may not have anything to do with the problem but will solve the known problems of SR-1 version.

Happy hunting.

by tranman

We had this problem some time ago. Is it possible that the exe was generated on a PC where VB was not at SP 5? We had a working program, which was recompiled by a programmer whose PC had been rebuilt and we forgot to install SP5. Program quit working, but when we tried it on an old version of the database (Access 97), it worked fine.

This discussion is closed to new replies.