Re: Problem with Doevents
- From: inquirer <noreply@xxxxxxxxxxx>
- Date: Tue, 03 Jan 2006 08:31:51 +1100
You keep referring to your form as "Userform1." Is that a naming convention you use or is this VBA code? VBA calls forms Userforms and a quick check just revealed that neither the Userform nor the label control has a .Refresh method. Also, the ProgressBar control (Version 5 SP2) doesn't have a .Refresh method either, although Version 6 SP4 does. All of that info is from Excel 97 so it's quite dated and possibly no longer accurate, but it does seem to mirror what you're seeing, which is why I ask if it's *really* VB6 code and not VBA.
RW
Firstly, Userform1 is just a name I gave to the form.
Secondly, I originally used this progress bar form in VBA (I obtained it from another website) and, after some modifications, it worked perfectly. I then saved the form as Userform1.frm and added this as a form to my VB6 program - it got added under "Designers" not "Forms".
I can access the object and code in VB6 for Userform1 as for a Form and it all looks ok.
The Frameprogress and Labelprogres are just names I gave to a frame and label in the form.
So although the original Userform1 was set up in VBA, I copied it to VB6. I guess that frames and labels must be somewhat different in VBA and VB6 or that a "Designers" are somewhat different from Forms.
I suppose the easy way out is to start from scratch and build the equivalent of Userform1 as a Form in VB6 when the Refresh method should be available.
Chris .
- References:
- Re: Problem with Doevents
- From: inquirer
- Re: Problem with Doevents
- From: J French
- Re: Problem with Doevents
- From: inquirer
- Re: Problem with Doevents
- From: RonW
- Re: Problem with Doevents
- Prev by Date: Re: problem with RegQueryValueEx (long)
- Next by Date: Re: Chunk of code INSIDE a Timer or in EXTERNAL routine (to speed up)?
- Previous by thread: Re: Problem with Doevents
- Next by thread: Re: Problem with Doevents
- Index(es):
Relevant Pages
|