Access 2000 on Windows XP

[Christine Connolly]

Is there a way to run Access 2000 through Windows XP
without having to convert the entire database? I work in
an office that shares an Access 2000 database. All of the
users are currently running Windows 2000 but a few of the
users would like to switch to Windows XP.

Thank you in advance for ideas/help!

 

[Keith Tizzard]

I have a database developed under Office 2000/Windows 2000 which
runs successfully on a machine with OfficeXP/WindowsXP.

However if I then alter any VB code on the latter, the program fails.

Any ideas?

-----Original Message-----
Hi Christine,

Whether you are using Windows 2000 or Windows XP shouldn't make any
difference to an Access 2000 database.

If you're muddling Windows 2000/XP and Office 2000/XP (easily done) it
still shouldn't matter: Access 2002 (the version in Office XP) by
default uses the same file format as Access 2000.

Is there a way to run Access 2000 through Windows XP
without having to convert the entire database? I work in
an office that shares an Access 2000 database. All of the
users are currently running Windows 2000 but a few of the
users would like to switch to Windows XP.

Thank you in advance for ideas/help!

John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.

 

[John Nurick]

I have a database developed under Office 2000/Windows 2000 which
runs successfully on a machine with OfficeXP/WindowsXP.

However if I then alter any VB code on the latter, the program fails.

Any ideas?

Symptoms: "The program fails".

Diagnosis: Something's gone wrong.

John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.

 

[Keith Tizzard]

John

Thanks for that diagnosis. I would never have come to that conclusion.

The problem is that working program developed under Office2000/
Windows2000 continues to work under OfficeXP/WindowsXP until it is
altered under the latter. The error is Ithat the program crashes with an
option to send an error report to Microsoft. The reply to this is not
helpful.

The question is "Why does altering the program under XP cause an
error?"

-----Original Message-----

I have a database developed under Office 2000/Windows 2000 which
runs successfully on a machine with OfficeXP/WindowsXP.

However if I then alter any VB code on the latter, the program fails.

Any ideas?

Symptoms: "The program fails".

Diagnosis: Something's gone wrong.

John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.

 

[John Nurick]

Keith,

I cannot look over your shoulder and am not clairvoyant.

Do you have the current Windows XP and Office XP service packs
installed?

What sort of an application is it? MDB, ADP or what?

Does the application crash when you merely edit a VBA module? when you
save the project? when you compile it? or when you actually run the
application?

If the last, does it crash as soon as you open the application or later?
If "as soon", what happens if you disable any autoexec macros or other
code that runs automatically when you open the application? If the
latter, which actual VBA statement is causing the crash? (find out by
stepping through the code).

If you create a new database (or Access project) in Access XP and import
all the objects from the old one, do things get any better?

John

Thanks for that diagnosis. I would never have come to that conclusion.

The problem is that working program developed under Office2000/
Windows2000 continues to work under OfficeXP/WindowsXP until it is
altered under the latter. The error is Ithat the program crashes with an
option to send an error report to Microsoft. The reply to this is not
helpful.

The question is "Why does altering the program under XP cause an
error?"

-----Original Message-----

I have a database developed under Office 2000/Windows 2000 which
runs successfully on a machine with OfficeXP/WindowsXP.

However if I then alter any VB code on the latter, the program fails.

Any ideas?

Symptoms: "The program fails".

Diagnosis: Something's gone wrong.

John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.

John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.