hi Kevin,
we use showcursor to catch the mouse problem:

************************************************************
Uses "user32.dll"
   ShowCursor(siCursor CWORD) CWORD         ; //   Displays or hides the
cursor.
{Parameters: 
   •    bShow, Type: BOOL
      If bShow is TRUE, the display count is incremented by one. 
      If bShow is FALSE, the display count is decremented by one.
Return Value:
• Type: int
  The return value specifies the new display counter.
Remarks: 
This function sets an internal display counter that determines whether the
cursor should be displayed. 
The cursor is displayed only if the display count is greater than or equal
to 0. 
If a mouse is installed, the initial display count is 0. 
If no mouse is installed, the display count is –1.      }

endUses

method cmShowCursor(lg Logical)
var
   si                  Smallint
endVar

   switch
   ; //   False, no = hide mouse
      case lg = No: 
         si = ShowCursor(0)          ; //   decrement by one
         while si >= 0
            si = ShowCursor(0) 
         endWhile
   ; //   True, yes = show mouse
      case lg = Yes: 
         si = ShowCursor(1)         ; //   increment by one
         while si < 1
            si = ShowCursor(1) 
         endWhile
   endSwitch   
endMethod
************************************************************

And we call executeSQL like this:

method run(var eventInfo Event)

   ...

   cmShowCursor(No)
   try
      if not itemSQL.executeSQL(dbSQL) then
         fail()
      endIf
   onFail
   ; //   save error

   ; //   Cursor wieder anzeigen
      cmShowCursor(Yes)

   ; //   error handling

   endTry

   cmShowCursor(Yes)


endMethod

Hope this helps ... 


"Kevin Zawicki" <numberjack@wi.rr.com> wrote:
>
>AS I switch processes over to localSQL I notice that on some larger procs
>the mouse changes to the Win10 "hourglass" circle, more. Specifically during
>localSQL executing. It is not any slower (mostly same or faster). But sometime
>the "hourglass" circle stays on screen after proc is complete until I move
>the mouse. Not really anything wrong, but is is misleading to the user.
>
>Anyone else see this?