Access 2000 will not function with WinXP Pro

message from =?Utf-8?B?TmFuY3k=?= on 27 May 2004

I have an application I wrote in Access 2000 on my old Win98 computer. I now have a new computer with WinXP Pro on which I installed my Access 2000 program. The application that I developed does not function properly. Many of the command buttons give error messages and often the application will not close. The message to send to Microsoft keeps coming up and then Access shuts down. A new file is written each time Access shuts down with the same name as my application with a ending extension of .ldb. This file type says that it is Access.LockFile.9 I feel that this has something to do with the network capability of WinXP, but I am not on a network. The application still works fine on my Win98 laptop and I even checked it on another persons computer that has Access 2000 with Win98. It seems to be the operating system. What can I do?

Tom Wickerath replied to =?Utf-8?B?TmFuY3k=?= on 27 May 2004

Hi Nancy,

With Access closed, use Windows Explorer to navigate to the folder that contains your database.
Delete all locking database files (*.ldb). A locking database file is normally created when you
start Access. It should be deleted automatically when you close the database, or in the case of
a shared database, when the last user has exited. When Access is not running, and you're sure no
other users have your database open (if on a shared drive), you should not see a .ldb file.

Can you reproduce this problem using a different Access database? Try copying another Access
database from your Win98 computer to this new PC to use as a test. If you experience similar
behavior, the problem may not be related to this particular application. You might want to look
at issues discussed in this KB article (even though it specifically mentions Windows 2000):

How To: Troubleshoot Fatal System Errors in Access 2003 When Access 2003 Is Running on the
Windows 2000 Operating System
http://support.microsoft.com/?id=825444

Have you applied the latest service pack to Windows XP Pro?
What about your installation of Office 2003? (I think SP1 is available, but I'm not positive)

And, just in case you already digitally signed your database in Access 2003, here is a new bug
that might be affecting you:

BUG: Access quits unexpectedly when you open a digitally-signed database with grouped controls in
Access 2003
http://support.microsoft.com/?id=833877

(Don't we all just love this new macro security stuff *+&^%$#@ ).

Tom
__________________________________

"Nancy" <anonymous@discussions.microsoft.com> wrote in message
news:3252E920-994A-4273-9465-6A3FC508BED0@microsoft.com...

I have an application I wrote in Access 2000 on my old Win98 computer. I now have a new computer
with WinXP Pro on which I installed my Access 2000 program. The application that I developed does
not function properly. Many of the command buttons give error messages and often the application
will not close. The message to send to Microsoft keeps coming up and then Access shuts down. A
new file is written each time Access shuts down with the same name as my application with a
ending extension of .ldb. This file type says that it is Access.LockFile.9 I feel that this has
something to do with the network capability of WinXP, but I am not on a network. The application
still works fine on my Win98 laptop and I even checked it on another persons computer that has
Access 2000 with Win98. It seems to be the operating system. What can I do?

=?Utf-8?B?TmFuY3k=?= replied to Tom Wickerath on 30 May 2004

Thank you for all your suggestions. None of these apply to my situation. The few applications that I have written in Access 2000 on my Win98 system do not work properly on WinXP Pro. I do not have Access 2003.

I have applied all the service patches and the Jet 8 update. On another post I was given several suggestions on how to solve the problem which I tried - none have worked.

There is something about the way my system is set up that is causing this problem. The same applicaiton works on my son's computer with Access 2000 and WinXP Home. The application works fine on Win98 - just not my new computer with WinXP Pro.

I am at my wits end - I don't know what else to do. I will try any more suggestions that you might have.

Tom Wickerath replied to =?Utf-8?B?TmFuY3k=?= on 31 May 2004

I'm not sure how you arrived at the conclusion that "None of these apply to my situation" so
fast. There is A LOT to check out in the KB article I referenced, such as an incompatible video
driver, memory conflicts (including possibly a bad memory chip), or perhaps a damaged hard drive
(ie. bad sectors).

If I understand you correctly, none of the databases that you wrote using your Win 98 PC are
functional on your new PC. Is this correct? If so, this is pointing to either a damaged
installation of Access on your new PC, or some type of hardware conflict or failure. Can you
create a brand new database from scratch on your new PC, complete with command buttons, that
works properly? Did you install the sample Northwind database when you installed Access on your
new PC? If not, pull out your CD installation set and install it. Does it work okay? Are you
seeing strange behavior in any other applications, such as Word, Excel, Outlook (or Outlook
Express)? If so, this could be further evidence of hardware failure.

Have you tried clicking on Help > Detect and Repair... in Access. Note that you may need your
installation CD handy to complete this process.

From your initial message: "Many of the command buttons give error messages ...."

What are the error messages that you are receiving?

and

"This file type says that it is Access.LockFile.9 I feel that this has something
to do with the network capability of WinXP, but I am not on a network."
Here is a KB article that tells you more about .ldb files:

Introduction to .ldb Files
http://support.microsoft.com/?id=208778

Tom

PS. Please do not delete the previous messages if you reply. Sometimes, I receive replies to
messages, but I never see the original messages. I'm sure I'm not the only one who has this
happen periodically. If you simply reply, but delete the previous messages, you may be
preventing someone from reading the entire conversation.
_______________________________________

"Nancy" <anonymous@discussions.microsoft.com> wrote in message
news:101CC563-D968-4657-A851-87C25E7F66C4@microsoft.com...

Thank you for all your suggestions. None of these apply to my situation. The few applications
that I have written in Access 2000 on my Win98 system do not work properly on WinXP Pro. I do not
have Access 2003.

I have applied all the service patches and the Jet 8 update. On another post I was given several
suggestions on how to solve the problem which I tried - none have worked.

There is something about the way my system is set up that is causing this problem. The same
applicaiton works on my son's computer with Access 2000 and WinXP Home. The application works
fine on Win98 - just not my new computer with WinXP Pro.

I am at my wits end - I don't know what else to do. I will try any more suggestions that you
might have.

_______________________________________

"Tom Wickerath" <AOS168RemoveThisSpamBlock@comcast.net> wrote in message
news:VLudnZXQLoq0USvdRVn-hg@comcast.com...

Hi Nancy,

With Access closed, use Windows Explorer to navigate to the folder that contains your database.
Delete all locking database files (*.ldb). A locking database file is normally created when you
start Access. It should be deleted automatically when you close the database, or in the case of
a shared database, when the last user has exited. When Access is not running, and you're sure no
other users have your database open (if on a shared drive), you should not see a .ldb file.

Can you reproduce this problem using a different Access database? Try copying another Access
database from your Win98 computer to this new PC to use as a test. If you experience similar
behavior, the problem may not be related to this particular application. You might want to look
at issues discussed in this KB article (even though it specifically mentions Windows 2000):

How To: Troubleshoot Fatal System Errors in Access 2003 When Access 2003 Is Running on the
Windows 2000 Operating System
http://support.microsoft.com/?id=825444

Have you applied the latest service pack to Windows XP Pro?
What about your installation of Office 2003? (I think SP1 is available, but I'm not positive)

And, just in case you already digitally signed your database in Access 2003, here is a new bug
that might be affecting you:

BUG: Access quits unexpectedly when you open a digitally-signed database with grouped controls in
Access 2003
http://support.microsoft.com/?id=833877

(Don't we all just love this new macro security stuff *+&^%$#@ ).

Tom
__________________________________

"Nancy" <anonymous@discussions.microsoft.com> wrote in message
news:3252E920-994A-4273-9465-6A3FC508BED0@microsoft.com...

I have an application I wrote in Access 2000 on my old Win98 computer. I now have a new computer
with WinXP Pro on which I installed my Access 2000 program. The application that I developed does
not function properly. Many of the command buttons give error messages and often the application
will not close. The message to send to Microsoft keeps coming up and then Access shuts down. A
new file is written each time Access shuts down with the same name as my application with a
ending extension of .ldb. This file type says that it is Access.LockFile.9 I feel that this has
something to do with the network capability of WinXP, but I am not on a network. The application
still works fine on my Win98 laptop and I even checked it on another persons computer that has
Access 2000 with Win98. It seems to be the operating system. What can I do?

=?Utf-8?B?TmFuY3k=?= replied to Tom Wickerath on 31 May 2004

I did try the references you sent, but they were for Access 2003 and I have version 2000. I will try the Northwind application. I did try the Detect and Repair and it didn't change anything.

I feel that there is something wrong with my system set up. All my other programs work just fine, especially the Microsoft applications. I did find out about the Access.LockFile9 file.

The error message that I get when I click a command button is something like "this is not available right now" or something is misspelled. The message differs and sometimes I don't get a message at all, nothing happens the button just doesn't work. Then when I close, the shut down will not work and I have to Ctrl Alt Delete to get out of Access.

Tom Wickerath replied to =?Utf-8?B?TmFuY3k=?= on 31 May 2004

Nancy,

A lot of the same issues apply equally well with earlier versions of Access, versus Access 2003.
Memory conflicts, bad video drivers, bad sectors on a hard drive, etc. etc. are not limited to
Access 2003 running on Windows 2000. Such conditions can affect Access 2000 running on Windows
XP just as well. A lot of KB articles include a specific version of Access in the title, when
they really apply to other versions as well.

Can you create a brand new database from scratch on your new PC, complete with command buttons,
that works properly? If the answer is no, then there is likely no problem with the databases you
created on your Win. 98 system.

Okay, then you might want to try:

1.) completely uninstall Office 2000
Use http://support.microsoft.com/?id=252566 as a guide (even though it is not written
specifically for Win XP).
2.) clear out your temporary folder
3.) do a scandisk followed by a defrag
4.) re-install Office 2000
5.) re-apply the service packs through SP-3.
6.) reinstall the Jet SP8 update
7.) clear out your temporary folder one more time to finish the process

_______________________________________

"Nancy" <anonymous@discussions.microsoft.com> wrote in message
news:6D7EB920-9DDD-4724-92DB-F5ADDB52453D@microsoft.com...

I did try the references you sent, but they were for Access 2003 and I have version 2000. I will
try the Northwind application. I did try the Detect and Repair and it didn't change anything.

I feel that there is something wrong with my system set up. All my other programs work just fine,
especially the Microsoft applications. I did find out about the Access.LockFile9 file.

The error message that I get when I click a command button is something like "this is not
available right now" or something is misspelled. The message differs and sometimes I don't get a
message at all, nothing happens the button just doesn't work. Then when I close, the shut down
will not work and I have to Ctrl Alt Delete to get out of Access.

Tom Wickerath replied to Tom Wickerath on 31 May 2004

PS.
HOW TO: Completely Remove Access 2000 from Your Computer
http://support.microsoft.com/?id=203370

_____________________________________

"Tom Wickerath" <AOS168RemoveThisSpamBlock@comcast.net> wrote in message
news:zNydnaIHQaavVSbdRVn-jA@comcast.com...

Nancy,

A lot of the same issues apply equally well with earlier versions of Access, versus Access 2003.
Memory conflicts, bad video drivers, bad sectors on a hard drive, etc. etc. are not limited to
Access 2003 running on Windows 2000. Such conditions can affect Access 2000 running on Windows
XP just as well. A lot of KB articles include a specific version of Access in the title, when
they really apply to other versions as well.

Can you create a brand new database from scratch on your new PC, complete with command buttons,
that works properly? If the answer is no, then there is likely no problem with the databases you
created on your Win. 98 system.

Okay, then you might want to try:

1.) completely uninstall Office 2000
Use http://support.microsoft.com/?id=252566 as a guide (even though it is not written
specifically for Win XP).
2.) clear out your temporary folder
3.) do a scandisk followed by a defrag
4.) re-install Office 2000
5.) re-apply the service packs through SP-3.
6.) reinstall the Jet SP8 update
7.) clear out your temporary folder one more time to finish the process

_______________________________________

"Nancy" <anonymous@discussions.microsoft.com> wrote in message
news:6D7EB920-9DDD-4724-92DB-F5ADDB52453D@microsoft.com...

I did try the references you sent, but they were for Access 2003 and I have version 2000. I will
try the Northwind application. I did try the Detect and Repair and it didn't change anything.

I feel that there is something wrong with my system set up. All my other programs work just fine,
especially the Microsoft applications. I did find out about the Access.LockFile9 file.

The error message that I get when I click a command button is something like "this is not
available right now" or something is misspelled. The message differs and sometimes I don't get a
message at all, nothing happens the button just doesn't work. Then when I close, the shut down
will not work and I have to Ctrl Alt Delete to get out of Access.

=?Utf-8?B?TmFuY3k=?= replied to Tom Wickerath on 31 May 2004

Thank you for your help. I printed out all the instructions for uninstalling Office 2000. I am hoping that I don't have to do that. I already tried uninstalling Access 2000 and reinstalling. Then my SP3 update didn't want to go back in. Anyway -- I just uninstalled McAfee antivirus and installed Norton antivirus. I also turned off 6 items loaded on startup that I don't think I need. (Real Player, Quick Time, Works Update, Acrobat Assistant, MS Office, Music Match). At the moment my application is working. I don't know what was causing the problem, but I hope it doesn't return.

=?Utf-8?B?TmFuY3k=?= replied to =?Utf-8?B?TmFuY3k=?= on 1 Jun 2004

Tom Wickerath replied to =?Utf-8?B?TmFuY3k=?= on 1 Jun 2004

Hi Nancy,

1.) Does a copy of the Northwind sample database work as expected on your PC and
2.) Can you create a brand new database from scratch on your PC, complete with command buttons
that work?

Tom
_________________________________________

"Nancy" <anonymous@discussions.microsoft.com> wrote in message
news:B3E17AE6-D0DA-474C-BD4B-C03A8D6D7206@microsoft.com...

Archived message: Access 2000 will not function with WinXP Pro (MS Access Forms)