Charlotte Foust
cfoust at infostatsystems.com
Mon Sep 15 10:40:49 CDT 2008
Gustav, Background workers are easy to create and use, and are the lazy programmer's friend! Our forms are so complex (because of the "intuitive" behavior requirements, not the inherent design) (all right... SOMETIMES because of the inherent design ;~>) that sometimes a background worker is the only practical way to handle something that needs to happen but isn't legal or doesn't work properly within a routine. In other words, we use them a lot. We have some standard objects, like a "wait" form that uses a background worker to keep it updated and it works fine. Charlotte Foust -----Original Message----- From: dba-vb-bounces at databaseadvisors.com [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of Gustav Brock Sent: Monday, September 15, 2008 2:05 AM To: dba-vb at databaseadvisors.com Subject: [dba-VB] VS2008: ProgressBar displays on XP, not on Vista Hi all I run a simple routine copying data between three databases in six steps. This lasts for about two minutes; in between a ProgressBar is advanced. This works fine when the app runs under WinXP, but under Vista 32-bit with the Aero interface either nothing happens or the ProgressBar updates once at some random step. The general advice is to use the BackgroundWorker for such tasks like the series of updates, but I'm lazy and wonder if a small trick can bring the ProgressBar to the surface and update under Vista as well. Any hints? /gustav _______________________________________________ dba-VB mailing list dba-VB at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-vb http://www.databaseadvisors.com