Migrating Access database from NT to Windows 2000? Is there any is

[Matrix]

Is there any issue migrating Access 2000 database from NT to Windows 2000? I
have application which use Access 2000 database. As lots of users were on NT
4.0 they are getting migrated to Windows 2000. What I have found that during
the migration process we just copy the database from NT to Widows 2000
machine.

The problem is after the user start using the application they started
getting corrupting their database after the migration. The application build
is same so same code for 2 platforms and getting database corrupted. The jet
drive is 4.0. Does any has suggestion?

 

[Immanuel Sibero]

Hi Matrix

Windows 2000 - All service packs installed?
Access 2000 and Jet 4.0 - All service packs installed?
Are you using the FE/BE setup?

Additional information:

http://www.granite.ab.ca/access/corruption/causes.htm

Immanuel Sibero

 

[Matrix]

First of all Thanks Immanuel.

Yes, Windows 2000 has sp4 installed.
Yes, Jet 4.0 and all the service packs installed on the client machine. We
don't install Access (never before migration).
Yes, It is same hardware (I mean same laptop that we are reimaging).

I am not sure what do you mean by FE and BE. If you meant to be Front End
and Back end than yes we do installed the application and resotre the
database which was backed up on NT. I hope this help.

 

[Immanuel Sibero]

Matrix,

I am not sure what do you mean by FE and BE. If you meant to be Front End
and Back end than yes we do installed the application and resotre the
database which was backed up on NT. I hope this help.

I did mean Front End / Back End within the context of MS Access. An MDB or
MDE that contains forms, queries, reports, etc (Front End) located on each
user's workstation and an MDB containing tables only located on a *share*
folder on the server. All users should have full access to the share folder.

From your post, I'm not sure if you're using Access as the Front End. Are
you using Access as your Front End? Any specific error messages?

You might also run through the website link I gave you earlier re:
corruptions. As you can see corruptions can be caused by anything from
hardware to software.


Immanuel Sibero

 

[Matrix]

Thanks for your reply. I am using visual basic 6.0 application as front end
using dao and jet driver 4.0 to connect to MDB. This application is installed
on all client machine and have their individual databases. Once they do their
work offline they can connect to network send the request to the server and
get their response back to the local database. I hope this will help. I will
go over the link that you provided.

 

[Immanuel Sibero]

Hi Matrix,

I have to say that the fact that you're using VB6.0 as a front-end probably
introduces other possibilities. I was under the assumption that you were
using Access MDB/MDE as a front end. I have limited experience with VB6.0 as
a front-end to an MDB. You might want to start a fresh thread so that you
will get more exposure to the experts.

Should you decide to start a new thread, additional detail would be helpful:
- VB6.0 as the front end.
- Any error message?
- You're stating that users work offline and then connect to the network,
I'm assuming the mdb that's corrupting is the one on the network?
- Is it possible to run everyting locally? i.e. move the mdb on the network
to a local drive and try to reproduce the corruption?

HTH,
Immanuel Sibero