ERR: Unrecognized database format! VB6 DAO3.5 & DAO3.6

[Steve Hebert]

I have a multi-user client that is getting this error at least once a day.
After Repairing and compacting the Access 97 database, they are ok for a
while. Jetcomp.exe does not work either, in fact the client claims it
occurs faster.

Trying to isolate the issue I created a loop to open and close a database
forever. After opening the Database 300,000 times or so I get the error.
Not sure if it is related to the clients problem however I should get the
error at all.

I have tried WIN95, WIN98, WINNT, WIN2000.
VB6 and VB6 SP3
DAO 3.5 and DAO 3.6

dim db as DAO.database
dim lCnt as long

bDoit = True
Do While bDoit
set db = OpenDatabase("c:\temp\temp.mdb") ' Any old 97 database
lCnt = lCnt + 1
Text1.text = lCnt
'Just a text box to visualize to where you are.
Text1.Refresh
db.close
' Close it down
set db = nothing
dbEngine.Idle dbRefreshCache 'Without
this line the error occurs faster about 100,000 times.
Loop

I have searched MSDN KBs. No Help. Getting ready to call Microsoft. Any
help appreciated?

[Microsoft Developer Support]

Steve,
I am currently trying to repro the problem. I will post new information to
the newsgroup when it becomes available.

Thanks,
Terrell A.
Microsoft Developer Support

[Microsoft Developer Support]

[Microsoft Developer Support]

Steve,
What type of Network are you on? Novell or NT?

Thanks,
Terrell A.

[Steve Hebert]

NT

Microsoft Developer Support <60...@microsoft.com> wrote in message
news:ZGFxj8Tq$GA...@cppssbbsa01.microsoft.com...

[Roy]

We get the same problem and our platform is Win95 there is an article
http://support.microsoft.com/support/kb/articles/q238/4/01.asp

but the code example here doesn't seem to work properly

Roy

Microsoft Developer Support <60...@microsoft.com> wrote in message

news:XDadXuHq$GA....@cppssbbsa01.microsoft.com...

[Microsoft Developer Support]

Steve,
Your sample probably does not relate to the problem your customers are
seeing. I ran your sample all day no problems. The count was in the
millions. This was on an NT 4.0 sp6 MDAC 2.5 machine. I'm not sure what
your customer application is doing, but corruption could be happening for a
number of reasons. Here is an artilce that discusses the most common
reasons:

ACC: Jet Database Engine 3.x Error Messages Due to Corruption [access]
ID: Q182867 CREATED: 23-MAR-1998 MODIFIED: 18-FEB-2000
WINDOWS:7.0,97
WINDOWS
PUBLIC | kberrmsg

======================================================================
----------------------------------------------------------------------------
---
The information in this article applies to:

- Microsoft Access versions 7.0, 97
----------------------------------------------------------------------------
---

Novice: Requires knowledge of the user interface on single-user computers.

SUMMARY
=======

This article discusses the three most common error messages returned by the
Microsoft Jet database engine 3.x that denote some form of corruption in the
database. The article discusses what the messages mean and how to resolve
the
issue(s) causing the error.

MORE INFORMATION
================

The following errors typically denote some form of corruption in the
database.

Error Number 3197::

Error message:

The Microsoft Jet database engine stopped the process because you and
another
user are attempting to change the same data at the same time.

Cause/Problem:

This error typically occurs when a long value column (an OLE or MEMO
data-type) has bad data stored in it. Long value columns are typically
stored
in a separate page from the page that the row is stored in. If a long
value
column is present in the table schema, the Jet database engine will
attempt
to read the long value page when reading the row of data. In order to
read
the long value page, there is a pointer in the row of data. This error is
generated when the Jet database engine cannot properly read the long
value
page from the pointer present in the data row. When viewing a row that
exhibits this behavior in Microsoft Access data-windows, the user will
typically see the number sign (#) for the entire row.

Error Number 3343:

Error message:

Unrecognized database format 'databasename.mdb'.

Cause/Problem:

This is typically caused when the Jet database engine was improperly shut
down during the process of writing to disk.

Error Number 3015:

Error message:

'databasename.mdb' isn't an index in this table. Look in the Indexes
collection of the TableDef object to determine the valid index names.

Cause/Problem:

This error message is typically caused when there is an index missing on
the
MSysObjects table. This is typically caused if the repair process is
aborted.

RESOLUTION
----------

The Microsoft Jet database engine version 3.51 has an enhanced compact
process
designed to remedy the problems (if possible) described in the "More
Information" section. The improved compact process now assumes all the
functionality of the repair process, and therefore it is no longer
recommended
that you use the Jet database engine repair process.

NOTE: The Microsoft Jet database engine version 3.51 update is designed for
Microsoft Access 97. You can run the compact utility on a database created
in an
earlier version of Microsoft Access; however, running the compact utility,
"JETCOMP.exe", requires that Microsoft Access 97 be installed on your
computer.

For more information about downloading the Jet database engine 3.51, please
see
the following article in the Microsoft Knowledge Base:

Q172733 ACC97: Updated Version of Microsoft Jet 3.5 Available for
Download

REFERENCES
==========

For more information about the enhanced compact process of the Jet database
engine 3.51, please see the following file, which is included as part of the
Jet35sp3.exe (Jet 3.51 update) download:

Jet35SP3.doc

For more information about Microsoft Access 97 error codes, search the Help
Index
for "reserved error codes," or ask the Microsoft Access 97 Office Assistant.

For more information about repairing Jet databases, please see the following
article in the Microsoft Knowledge Base:

Q109953 ACC: How to Repair a Damaged Database

Additional query words: inf

======================================================================
Keywords : kberrmsg
Version : WINDOWS:7.0,97
Platform : WINDOWS
Issue type : kbinfo
============================================================================
====

[Steve Hebert]

I have read the article. It pertains to reading a Access 2000 database
with DAO. That is not the case. The Access 97 database ends up
corrupted. Have to repair and compact to get back in. In some cases, the
DB is in between 97 and 2000.
97 says "Unrecognized database format!", 2000 says it is a earlier version.

I have relinked my app with DAO3.6 waiting to see if it helps my client.
However, the test program still fails. Microsoft support tells me that
any routine opening and closing a database in a loop will cause memory
leaks. I understand that and now I am trying to focus in on why 1 client
is getting the error daily.

Steve

Roy <roy_...@www.yahoo.co.uk> wrote in message
news:7jBL4.4368$UC.52455@news2-hme0...

> We get the same problem and our platform is Win95 there is an article
> http://support.microsoft.com/support/kb/articles/q238/4/01.asp
>
> but the code example here doesn't seem to work properly
>
> Roy
>
>
>
> Microsoft Developer Support <60...@microsoft.com> wrote in message
> news:XDadXuHq$GA....@cppssbbsa01.microsoft.com...
> > Steve,
> > I am currently trying to repro the problem. I will post new information
to
> > the newsgroup when it becomes available.
> >
> >