Question MS Access White Screen

nzcncf

New member
Local time
Today, 01:53
Joined
Aug 14, 2014
Messages
8
Our client has about 10 end users on Terminal Serve, and they occassionally get white screen error. The event log show following error message"
The program MSAccess.exe version 14.0.7104.5000 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Problem Reports and Solutions control panel. Process ID: 51cc Start Time: 01cfb681b4d13efe Termination Time: 0" Event ID 1002.

Server has MS Access 2010 (SP2) runtime installed. The error happens randomly, and happen on a particular form. When user has updated form details, click EXIT button, the white screen occur. Any one has seen this 1002 error?

Thanks for the help
 
Haven't seen that error, but does each user run their own copy of the front end (it is split I hope)? I got odd errors with apps run on TS until I did that.
 
Thanks for the quick reply.

Yes, each user has their own copy of accde file. By the way the BE is SQL Server DB.

I have googled about this error, but found very little info about it.
 
What code does the Exit button contain, (show it)?
 
Put error handling in suspected code. Runtime simply flops belly-up if any unhandled error occurs. A nice tool for doing this is MZ-tools - download it.

Update: Your event id 1002 is a terminal server feature, apparently reacting to Access not doing its thing properly. So my advice stands: insert error handling.
 
Last edited:
I had another look, and think this happens when user first sees a white screen (Application Hang), and uses Task Manager (or Ctl + Alt + Del) to kill Access session. Therefore this is actually the result of user intervention.

I need to find out why user sees the white screen. One block of code create a DAO recordset, but not close it, and set it to nothing. Will this cause memory leaking, therefore cause the white screen? Any comments?
 
No and no. As answer to your first question.

Second question: If it hangs find out on what. An endless loop perhaps?
 
I have seen the white screen when Access is busy on a long process and the screen doesn't refresh. Seeing the code may help.
 

Users who are viewing this thread

Back
Top Bottom