🚀 go-pugleaf

--------------F58740EEC654DFCC83A48A2D
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Problem 1 :

     Check out the QueryUnload Event on the Form.

Problem 2 :

     Not too sure what you're after here.
     If you want to use TextBoxes, you're going to a get a cursor, like it
     or not, simply because that what Windows TextBoxes do.  You could try
     Disabling the Frames that the TextBoxes appear in - I think that
     might do the trick.  Out of curiousity, what's wrong with the .Locked
     property?  It would allow you the flexibility to 'unlock' the fields
     for some Users and not for others.

HTH,
    Phill  W.



--------------F58740EEC654DFCC83A48A2D
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Problem 1 :
<blockquote>Check out the <b><font size=-1>QueryUnload</font></b> Event
on the Form.</blockquote>
Problem 2 :
<blockquote>Not too sure what you're after here.
<br>If you want to use TextBoxes, you're <i>going </i>to a get a cursor,
like it or not, simply because that what Windows TextBoxes do.&nbsp; You
could try Disabling the Frames that the TextBoxes appear in - I think that
might do the trick.&nbsp; Out of curiousity, what's wrong with the <b><font size=-1>.Locked</font></b>
property?&nbsp; It would allow you the flexibility to 'unlock' the fields
for some Users and not for others.</blockquote>
HTH,
<br>&nbsp;&nbsp;&nbsp; Phill&nbsp; W.
<br>&nbsp;
<br>&nbsp;</html>

--------------F58740EEC654DFCC83A48A2D--