Dan Waters
dwaters at usinternet.com
Mon Dec 31 09:57:34 CST 2007
Hi Rocky, The cause is indeed the requeries. The solution is to use Application.Echo False [Opening Code] Application.Echo True A caveat: If you are going to use this in production code, you must introduce error trapping into every procedure that could possibly be used during startup, and that error trapping must include the line: Application.Echo True I error trap every procedure, and include this line in every trap. Another caveat: While you are developing, if you have an error and you have error trapping turned on, then you will get a frozen screen and will need to End the app with Task Manager. Hope this Helps! Dan -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at Beach Access Software Sent: Monday, December 31, 2007 9:19 AM To: 'Access Developers discussion and problem solving' Subject: [AccessD] Screen Flutter Dear List: Legacy app. Continuous bound form with no sub-forms. When it opens it 'flutters' I guess what we always call here the 'flashing screen' phenomenon. It flashes or flutters 3-5 times during opening. There are a bunch of requeries and a couple of repaints in the code but that's not causing it because I comment them out one at a time and saw no change. Tried Me.Visible=false on entering the open event and Me.Visible=True before leaving the open event. No difference. So what's the most likely cause of the fluttering or flashing on open? MTIA Rocky -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com