Moving Access application to new platform results in error 3343

[Xavier]

Hello,

I am currently replacing a customer's network and during the migration I do
face an Access related issue.
The current network is made of a NT4 server and Win2000 workstations. In
this environment, there is an application (developed by a small SW house
that doesn't exist anymore) that seems to be VB and that uses access 97
runtime. This applications stores its data in a backend Access database (an
mdb file located on a network share).

The new network is made of Win2003 and WinXP workstations (that come with
Office 2003 basic edition: Outlook, Word & Excel. No Access). I can install
the client part on the XP workstations and I have copied the mdb file from
the old server to the new one (no one was using the DB at that time, so no
ldb related issues I assume). When I start the client I now get an error
3343 "unrecognized database format in ... \\path-to-mdb-file". I performed a
search in google but the information that I retrieved is related to
conversion issues between 97 and 2000+ formats which is irrelevant in my
case since the DB was never opened with Access 2000, XP or 2003.

Last but not least, we do not have the source of the application, so
tweaking the code is of no use for us.

Is there anything I can do on the infrastructure side in order to have the
application up and running again ?

Any help would be appreciated.

Xavier

 

[Albert D.Kallal]

since the DB was never opened with Access 2000, XP or 2003.

Are you sure?

Why not grab the original mdb file from the original backup on the nt box.

Does it work?

I have to assume the appcation in question when installed on a pc does
provide for means to "select" which data file to connect to.

Further, is he application a VB runtime..or a ms-access based runtime?

It is possible you are missing the old jet3.5 on your new machines?

 

[Xavier]

Hi Albert,

see inline for comments.

Thanks

Are you sure?
Yes.


Why not grab the original mdb file from the original backup on the nt box.

Does it work?

No.

The old environment is still running, while I am building the new one in
parallel. So, the mdb file I copied was used today in the old environment
without problem.

I have to assume the appcation in question when installed on a pc does
provide for means to "select" which data file to connect to.

No. It seems to be hardcoded. In the new environment I create the same drive
mappins as in the old one.

Further, is he application a VB runtime..or a ms-access based runtime?

good point. Could be an ms-access runtime (but I am no Access expert. All I
can tell is that the application is launched via a mde file)

It is possible you are missing the old jet3.5 on your new machines?

Could be. Could you tell me how to install this on new systems ?


Thanks for your help.

 

[Albert D.Kallal]

The old environment is still running, while I am building the new one in

parallel. So, the mdb file I copied was used today in the old environment
without problem.

Ok, so you have a mdb data part for the back end.....

good point. Could be an ms-access runtime (but I am no Access expert. All
I can tell is that the application is launched via a mde file)

ah...ok..if the front end is a mde file..then this is not a VB, but is a
ms-access application.
(this is good progress!!)

Could be. Could you tell me how to install this on new systems ?

I have to assume that the old system comes with a "installer"..and I have to
assume this includes the ms-access runtime....

It seems that you *can* launch the application...and it does start....?

If the runtime install occurs, then you should be ok in terms of having the
older jet installed.

are we assuming access 97? here?...likely?

Perhaps you give the access97 updates a try.

I would setup a test machine...and try the whole thing on a box without
having installed office (and especially a later version of ms-access).

You need to be able to test a bunch of different installs...and then throw
them out...and try again.

So, this kind of testing calls for virtual pc. You certainly need a test
environment to work on here...either a box, or even better would be virtual
pc. (then you can setup two imaginary machines...and one can even have the
back end with the correct path name/mapping).

Have you tried checking what version the mdb back end is?
(and, what version of access do you have...or is none installed?).

I not sure quite what I would try next. Remember, simple things like full
permissions to the back end are required (that means file create rights,
file delete rights....full rights to the back end dir).

Do you use a shortcut on the old machine....what does the shortcut look
like? This is kind of tough..since there is certainly 100's of simple
questions that take just seconds to ascertain if you know ms-access (for
example, the fact that you mentioned that a mde is launched means this is
ms-access, and not a VB application). My point is that likely a 1000's of
these small issues can be derived in about 5 minutes of time by someone who
knows there way around ms-access. You could try some more of the above
ideas.....if they don't work, then I would consider finding someone in your
area who can help you look at this stuff...

 

[Ron Hinds]

You need to do a Repair on the database (.mdb) file. Use JetComp, available
for download free from Microsoft:

http://support.microsoft.com/default.aspx?scid=kb;en-us;273956