My VB program uses SQL to retrieve information from several tables from an Access database and combines it with a couple other fields from two tables in a second Access database. Depending on the size of the first Access database and the speed of the users machine, this process can take from 5 seconds to many minutes (20-30 possibly). I don't want a user to think the system is hung after 15 minutes when it is still just crunching away (something we noticed and a beta tester commented on). A simple message to 'please wait while the table is created' is not sufficient to let the user know all is proceeding. I've added an animation control that displays while the program works away. If the program really does 'stop responding' and gets hung, does the animation stop as well? If the animation continues if the program is hung, then I don't see a compelling reason to include the animation. What else could accomplish this feedback to the user?
thanks,
Jim
thanks,
Jim