How to suppress MS Access warning while converting from 97 to 2000/2003 format

[Karen]

I'm using the following command to convert an access database in
Windows 2000 server with Office 2003.
msaccess "C:\test.mdb" /convert "C:\test1.mdb"

After conversion is completed, it prompts me the following message:
"After you have converted this file to Access 2000 File Format, the
new file cannot be shared with Access 97 users.
Any functionality specific to Access 2002 or later will not be
available in Access 2000.
For more information about conversion, click Help."

Is there any way to suppress this message?

I do not want to suppress the Open dialog where it asks you to perform
a database conversion due to incorrect format as specified in
KB824269.

 

[Douglas J. Steele]

I don't believe there is any way to suppress that message. However, since
you should be testing all of your conversions before turning them over to
your users, I don't see what it matters that the message appears.

 

[Karen]

Thank you for your reply.

However, I'm not simply converting the access database for my user.
I'm doing this as a work around for another problem I encountered.

The original problem is the error returned from the following query:

SELECT b.*
FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0', 'c:\test.mdb';'admin';'',
ReportType) AS b

Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: Cannot open database ''. It may
not be a database that your application recognizes, or the file may be
corrupt.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].

This error ONLY happens to Access 97 database. After access database
is converted to 2000/2003 format, the query works fine.

We've tried install/reinstalling ms jet 4.0 sp 8 a couple of times
before and after the Office installation. It works for a few days and
then not working again.

We know that the 97' access file is not corrupted as we can open the
database using this query from another SQL server.

So, we've concluded that cannot make this query works reliable with
Access 97' format. As a work around, I created a batch file to
convert the 97 access database and then run the query (trying to keep
things in 1 step for the user).

Perhaps you have insights on how to resolve this problem?
Thanks.

-- Karen

 

[david epsom dot com dot au]

I don't understand this error either, but if this is the
only reason you have for converting the A97 database on
the fly, use a DAO 3.6 object to do the conversion, rather
than an Access shell command. The method is CompactDatabase,
and there is no requirement for user interaction, (or
for a user login).

Thank you for your reply.

However, I'm not simply converting the access database for my user.
I'm doing this as a work around for another problem I encountered.

The original problem is the error returned from the following query:

SELECT b.*
FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0', 'c:\test.mdb';'admin';'',
ReportType) AS b

Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: Cannot open database ''. It may
not be a database that your application recognizes, or the file may be
corrupt.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].

This error ONLY happens to Access 97 database. After access database
is converted to 2000/2003 format, the query works fine.

We've tried install/reinstalling ms jet 4.0 sp 8 a couple of times
before and after the Office installation. It works for a few days and
then not working again.

We know that the 97' access file is not corrupted as we can open the
database using this query from another SQL server.

So, we've concluded that cannot make this query works reliable with
Access 97' format. As a work around, I created a batch file to
convert the 97 access database and then run the query (trying to keep
things in 1 step for the user).

Perhaps you have insights on how to resolve this problem?
Thanks.

-- Karen

"Douglas J. Steele" <NOSPAM_djsteele@NOSPAM_canada.com> wrote in message

I don't believe there is any way to suppress that message. However, since
you should be testing all of your conversions before turning them over to
your users, I don't see what it matters that the message appears.