Update - How to prefent 'Hard Flicker'

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Marshall & All -

I am still struggling with this issue, but I thought I would give additional
detail. Like I said, this issue (it seems), is most apparent, if the focus
switches to another application while Access is processing a large amount of
code. Both DAO & ADO are being used, but an empesis of DAO.

One of the 'Symptoms' of this 'State', is as follows:

I open the application from an icon.
WHile the application is loading, I switch to Outlook.
Switch back to the app, after I judge that the app has finished loading.
The opening form, which is opened by a function, triggered by an autoexec,
appears to not correctly 'Painted' on the screen. The top border is not
present, and the command buttons are non-functioning.
I exit the application, by clicking the 'X' in the top right corner of the
Access program.
After a slight pause, the flicker happens, and the only recourse is the
<ctrl><alt><Del>.
<ctrl><Break> does nothing.

I also have had this state happen when iterating through a TableDef
collection, AND it prompted a VISIBLE error. 'Ilegal DLL call'. Immeadiatly
after this error, the flicker state became present. Could it be related to
DAO???

Thanks for listening.
 
Try

1. Turning Echo off before processing begins, then on again after complete.

2. Also, turn on the hourglass for the user. While they can still use the
hourglass cursor to click around, most of the time users don't because they
know it means "Wait".

DoCmd.Hourglass True
DoCmd.Echo False
'Do processing
DoCmd.Echo True
DoCmd.Hourglass False

Outlook takes up a lot of the memory available, so other processes be forced
to wait until Outlook is done synchronizing itself (specifically Outlook
2003 when using Local Cache).

Also, if your users must wait an extraordinary period of time before the app
actually opens, this isn't ideal. If you can move some of the processing to
a later event or time, you should so the user has a better experience. For
instance, if the user is waiting for all items entered/changed yesterday to
process, update, etc, that may be better done when the user is not there to
see or wait for it.

Try a program like FMS, Inc's Total Visual Agent to process and run things
when the users are not around to need to wait for it to complete:
http://www.fmsinc.com/products/Agent/index.html

--
Troy

Troy Munford
Development Operations Manager
FMS, Inc.
www.fmsinc.com


"kalbrecht1972_hotmail_com"
Marshall & All -

I am still struggling with this issue, but I thought I would give additional
detail. Like I said, this issue (it seems), is most apparent, if the focus
switches to another application while Access is processing a large amount of
code. Both DAO & ADO are being used, but an empesis of DAO.

One of the 'Symptoms' of this 'State', is as follows:

I open the application from an icon.
WHile the application is loading, I switch to Outlook.
Switch back to the app, after I judge that the app has finished loading.
The opening form, which is opened by a function, triggered by an autoexec,
appears to not correctly 'Painted' on the screen. The top border is not
present, and the command buttons are non-functioning.
I exit the application, by clicking the 'X' in the top right corner of the
Access program.
After a slight pause, the flicker happens, and the only recourse is the
<ctrl><alt><Del>.
<ctrl><Break> does nothing.

I also have had this state happen when iterating through a TableDef
collection, AND it prompted a VISIBLE error. 'Ilegal DLL call'. Immeadiatly
after this error, the flicker state became present. Could it be related to
DAO???

Thanks for listening.
 
Back
Top