Results 1 to 6 of 6

Thread: problem with using vbHourglass

  1. #1

    Thread Starter
    New Member
    Join Date
    Jun 2000
    Posts
    12

    I am using 'vbHourglass' to set the cursor to an
    hourglass during the data retrieval.
    It doesn't work.
    I am using the statement -

    Screen.mousepointer = vbHourglass

    at the start of the Form_Load, and then set it back
    to vbArrow at the end of the procedure.

    Has anybody seen this type of problem ?

    Thanks

  2. #2
    PowerPoster 2.0 Negative0's Avatar
    Join Date
    Jun 2000
    Location
    Southeastern MI
    Posts
    4,367
    The only problem I could think of is that you call a sub that resets the mousepointer.

  3. #3
    Guest
    You procedure probably goes by really fast which does not allow much time for the Hourglass to show.

  4. #4

    Thread Starter
    New Member
    Join Date
    Jun 2000
    Posts
    12
    I am setting the vbHourglass in the sub that reads data
    from the database.
    Actually the read takes almost a minute. So I really need
    the hourglass to be shown.

  5. #5
    Fanatic Member
    Join Date
    Mar 2000
    Location
    That posh bit of England known as Buckinghamshire
    Posts
    658
    Try adding a "DoEvents" (cures almost everything) or "Me.Refresh" after seting the cursor.
    Iain, thats with an i by the way!

  6. #6
    transcendental analytic kedaman's Avatar
    Join Date
    Mar 2000
    Location
    0x002F2EA8
    Posts
    7,221
    Well the mousepointer must be over your form to be shown as a hourglass, if you have it invisble it will show a normal cursor. Actually doevents won't do anything in this case, by not having any threading at all your mousepoint wont return to nomal if you move your mouse outside the form
    Use
    writing software in C++ is like driving rivets into steel beam with a toothpick.
    writing haskell makes your life easier:
    reverse (p (6*9)) where p x|x==0=""|True=chr (48+z): p y where (y,z)=divMod x 13
    To throw away OOP for low level languages is myopia, to keep OOP is hyperopia. To throw away OOP for a high level language is insight.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width