Access 2000 DB - crashes after XP upgrade

[Charlie Samet]

I need some help...

I have several Microsoft Access 2000 databases that after upgrading to
Office 2002 they crash. What happens is when you open the database, after
several seconds Microsoft Office 2002 crashes with a general "Microsoft
Access has encountered a problem and needs to close."

I haven't found any solution for this yet. I've tried running Office in
safemode, no luck. These are databases that I've used for the last 3-4
years under 2000 and never had a problem until upgrading to 2002. It's
really weird, some of my databases converted over, some did not.

My databases do have extensive VBA to make things work. Could there be
some VBA code that is no longer compatible?

If you are aware of anything from 2000 that could not work in 2002, anything
that might cause the databases to become non-functional, I would appreciate
a response. Thanks.

Charlie

 

[Br@dley]

I need some help...

I have several Microsoft Access 2000 databases that after upgrading to
Office 2002 they crash. What happens is when you open the database,
after several seconds Microsoft Office 2002 crashes with a general
"Microsoft Access has encountered a problem and needs to close."

I haven't found any solution for this yet. I've tried running
Office in safemode, no luck. These are databases that I've used for
the last 3-4 years under 2000 and never had a problem until upgrading
to 2002. It's really weird, some of my databases converted over,
some did not.
My databases do have extensive VBA to make things work. Could there
be some VBA code that is no longer compatible?

If you are aware of anything from 2000 that could not work in 2002,
anything that might cause the databases to become non-functional, I
would appreciate a response. Thanks.

Charlie

Have you tried creating a new 2002 db and importing everything, rather
than convertingn it?

_When_ does it crash? It's most likely that your code references are
wrong. Starting with a new db will fix that.
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response

 

[Ron Hinds]

Get the latest Jet 4.0 Service Pack from Microsoft.

 

[Charlie Samet]

Have you tried creating a new 2002 db and importing everything, rather
than convertingn it?

_When_ does it crash? It's most likely that your code references are
wrong. Starting with a new db will fix that.
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response

Well, I did try improting everything in to a new database. Funny enough,
that works out ok (just tried that the other day). However, the reason I
did not want to have to do it this way is that I am using the Microsoft
Database security files (.mdw) to login to the database. When I move the
database over, I lose the security. I am considering just redoing the
security permissions in a clean database this way, and save myself the time
beating up on trying to get this thing to convert over ok.

Thanks for the tip!

 

[Br@dley]

Well, I did try improting everything in to a new database. Funny
enough, that works out ok (just tried that the other day). However,
the reason I did not want to have to do it this way is that I am
using the Microsoft Database security files (.mdw) to login to the
database. When I move the database over, I lose the security. I
am considering just redoing the security permissions in a clean
database this way, and save myself the time beating up on trying to
get this thing to convert over ok.
Thanks for the tip!

Yeah, you'll probably save yourself time that way even though it might
be a bit of a pain redoing all the permissions.

If it is the references though it might be fixable without having to
import to a new db.... but if you've already spent too much time poking
around trying to solve it it's probably worth a clean start for the
guaranteed fix.
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response