Numerous problems with Access 2000 and Windows XP

[Andrew Smith]

A couple of weeks ago our IT department replaced my Windows NT machine with
a Windows XP one. Since then I've had numerous weird things happen whilst
working on my Access applications. These are the symptoms:

1. The application periodically freezes. This happens at various times. The
Access window loses the focus to another application or to the VBA window.
Clicking the Access window justs gives beep, although the program will
respond to commands issued via the VBA intermediate window, and it is
possible to open the VBA window using Alt-F11.

2. The program crashes any time I try and edit the code in one particular
form. This only happens on one form, and only started today so it may have
nothing to do with the other issues (this is the first time that I have
edited the code on this form for some time). It happens as soon as I try and
save the VBA project. The main Access window goes white, and the only thing
to do is shut the App down with Ctrl-Alt-Del. Strangely the task manager
shows two instances of Access and VBA, but all disappear after clicking "End
Application".

3. The scroll bars in the database window sometimes don't work until the
window is moved a bit. Sometimes an object will open when I try and use the
scroll bars.

4. It is sometimes not possible to move or resize the table windows in the
query design grid or the relationships window. Usually this can be corrected
by selecting one of the fields first.

5. From time to time all the menus and toolbars disappear from the VBA
window. On one occasion this was followed by a crash soon after, so now I
immediately restart Access when I notice this.

I feel sure that most of these problems are related (although I'm not so
sure about number 2 as this is very specific to one form), and that they
must have something to do with the new PC.

If anyone has any suggestions I'd be most grateful as Access is hard enough
without all this!

 

[Andrew Smith]

Just remembered another one that I've seen at least three times:

6. "Duplicate declaration in the current scope" error in the code on the
start up form. I can't reproduce this, and it normally works fine.

 

[Allen Browne]

Answers embedded.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

A couple of weeks ago our IT department replaced my Windows NT machine with
a Windows XP one. Since then I've had numerous weird things happen whilst
working on my Access applications. These are the symptoms:

1. The application periodically freezes. This happens at various times. The
Access window loses the focus to another application or to the VBA window.
Clicking the Access window justs gives beep, although the program will
respond to commands issued via the VBA intermediate window, and it is
possible to open the VBA window using Alt-F11.

Try turning off Themes in XP. Right-click the screen, and choose Properties.
Set the Theme to Windows Classic. This avoids a number of situations that
appear to be related to faulty screen-metrics, i.e. WinXP cannot recognise
what was clicked.

Also worth double-checking you have not left Echo Off.

2. The program crashes any time I try and edit the code in one particular
form. This only happens on one form, and only started today so it may have
nothing to do with the other issues (this is the first time that I have
edited the code on this form for some time). It happens as soon as I try and
save the VBA project. The main Access window goes white, and the only thing
to do is shut the App down with Ctrl-Alt-Del. Strangely the task manager
shows two instances of Access and VBA, but all disappear after clicking "End
Application".

Yes, sounds like a corruption. Try rebuilding the database. Suggested steps:
http://allenbrowne.com/ser-47.html
Especially, make sure Name AutoCorrect is off.

Also, make sure you have the Service Pack 3 for Office 2000, and Service
Pack 8 for Jet 4. See the Downloads section at:
http://support.microsoft.com

Also a good idea to check you have SP1 for WinXP.

3. The scroll bars in the database window sometimes don't work until the
window is moved a bit. Sometimes an object will open when I try and use the
scroll bars.

This symptom is related to #1 above.

4. It is sometimes not possible to move or resize the table windows in the
query design grid or the relationships window. Usually this can be corrected
by selecting one of the fields first.
Ditto.


5. From time to time all the menus and toolbars disappear from the VBA
window. On one occasion this was followed by a crash soon after, so now I
immediately restart Access when I notice this.

Have not seen this. Is it possible that something is draining Windows
resources?

 

[Allen Browne]

Does the project compile okay?
(From the code window, Compile on Debug menu.)

The message basically means there are 2 things with the same name. If it
compiles fine and only occurs intermittently, make sure Name AutoCorrect is
off under:
Tools | General | Options.
For more info, see:
Failures caused by Name Auto-Correct
at:
http://allenbrowne.com/bug-03.html

 

[david epsom dot com dot au]

A couple of weeks ago our IT department replaced my Windows NT machine with
a Windows XP one.

And possibly neglected to apply the Office 2000 and Jet 4.0 service packs
after doing so.


(david)

 

[Andrew Smith]

Allen,

Many thanks. I reverted to the "Windows Classic" look and turned off the
Name-AutoCorrect first thing this morning. Since then I've spent about 6
hours working on this application with no problem at all (well, only the
ones of my own making anyway). Even the form that I couldn't edit yesterday
is now behaving normally without having to try anything else.

I actually had the Nam-AutoCorrect turned off on my old PC, but forgot to
change it when I got the new one. However, I'd probably never have thought
of the Windows XP Theme thing.

Thanks again,

Andrew

 

[Andrew Smith]

Yes the project compiles OK.

I've not seen the problem since I turned off Name AutoCorrect, so that could
well be it.

(BTW I can't access your web page).