Thread View: comp.lang.basic.visual.misc
4 messages
4 total messages
Started by Princess Morgiah
Mon, 06 Sep 1999 00:00
Two small problems
Author: Princess Morgiah
Date: Mon, 06 Sep 1999 00:00
Date: Mon, 06 Sep 1999 00:00
19 lines
1369 bytes
1369 bytes
Hi there , I recently started writing a program in Visual Basic 5.0 , which I'm new to . Can anyone out there help me with these two problems ? Problem One : How do I catch the following event : when a user clicks the close button the little X in the upright corner ) , I intend to ask him for confirmation ( database is open , really exit ? and that sort of stuff ) , but how do I do this ? Problem Two : How can I have a form without a cursor and without using the 'locked' properties ? The form only contains textboxes ( 32 ) , labels ( 32 ) and a few frames ... Thank you very much for your help , Princess Morgiah
Re: Two small problems
Author: JaReD
Date: Mon, 06 Sep 1999 00:00
Date: Mon, 06 Sep 1999 00:00
5 lines
906 bytes
906 bytes
for problem 1 experiment with the form_queryunload event for problem 2 how about creating your own cursor which just happens to be all transparent...this would be much better than messing around with the system configurations.
Re: Two small problems
Author: Phillip Ward
Date: Tue, 07 Sep 1999 00:00
Date: Tue, 07 Sep 1999 00:00
47 lines
2306 bytes
2306 bytes
--------------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. 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 <b><font size=-1>.Locked</font></b>
property? It would allow you the flexibility to 'unlock' the fields
for some Users and not for others.</blockquote>
HTH,
<br> Phill W.
<br>
<br> </html>
--------------F58740EEC654DFCC83A48A2D--
Re: Two small problems
Author: Princess Morgiah
Date: Wed, 08 Sep 1999 00:00
Date: Wed, 08 Sep 1999 00:00
112 lines
5198 bytes
5198 bytes
This is a multi-part message in MIME format.
------=_NextPart_000_0010_01BEF9F9.2995AB00
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
First of all , to everyone who replied : thank you ! You have helped me =
a lot ...
Second , to Phillip : the idea in Problem 2 was to have some sort of =
info screen , with a whole bunch of textboxes and labels . I didn't want =
to see a cursor in any of them ... I don't like using the .Locked =
property , because you can still place a cursor inside them , and select =
text . In my opinion , it gives the impression that these textboxes can =
be altered some way or other .
I solves it like this ( read this somewhere else in this NG , not sure =
where - thanks to whoever wrote this ) :
Private Sub txtTextBox_GotFocus()
cmdCommandButton.SetFocus
End Sub
With the cmdCommandButton the close button on my form .
Princess Morgiah
Phillip Ward wrote in message <37D4E190.747A36E5@tesco.net>...
Problem 1 :=20
Check out the QueryUnload Event on the Form.
Problem 2 :=20
Not too sure what you're after here.=20
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,=20
Phill W.=20
=20
=20
------=_NextPart_000_0010_01BEF9F9.2995AB00
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type><!doctype html public "-//w3c//dtd html 4.0 =
transitional//en">
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 face=3D"" size=3D3>First of all , to everyone =
who replied :=20
thank you ! You have helped me a lot ...</FONT></DIV>
<DIV><FONT color=3D#000000 face=3D"" size=3D3></FONT> </DIV>
<DIV>Second , to Phillip : the idea in Problem 2 was to have some sort =
of info=20
screen , with a whole bunch of textboxes and labels . I didn't want to =
see a=20
cursor in any of them ... I don't like using the .Locked property , =
because you=20
can still place a cursor inside them , and select text . In my opinion , =
it=20
gives the impression that these textboxes can be altered some way or =
other=20
.</DIV>
<DIV> </DIV>
<DIV>I solves it like this ( read this somewhere else in this NG , not =
sure=20
where - thanks to whoever wrote this ) :</DIV>
<DIV> </DIV>
<DIV>Private Sub txtTextBox_GotFocus()<BR> =20
cmdCommandButton.SetFocus<BR>End Sub</DIV>
<DIV> </DIV>
<DIV>With the cmdCommandButton the close button on my form .</DIV>
<DIV> </DIV>
<DIV>Princess Morgiah</DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; PADDING-LEFT: =
5px">
<DIV>Phillip Ward<PHILLIP.WARD@TESCO.NET> wrote in message <<A=20
=
href=3D"mailto:37D4E190.747A36E5@tesco.net">37D4E190.747A36E5@tesco.net</=
A>>...</DIV>Problem=20
1 :=20
<BLOCKQUOTE>Check out the <B><FONT size=3D-1>QueryUnload</FONT></B> =
Event=20
on the Form.</BLOCKQUOTE>Problem 2 :=20
<BLOCKQUOTE>Not too sure what you're after here. <BR>If you want to =
use=20
TextBoxes, you're <I>going </I>to a get a cursor, like it or =
not, simply=20
because that what Windows TextBoxes do. You could try =
Disabling=20
the Frames that the TextBoxes appear in - I think that might do =
the=20
trick. Out of curiousity, what's wrong with the <B><FONT=20
size=3D-1>.Locked</FONT></B> property? It would allow you =
the=20
flexibility to 'unlock' the fields for some Users and not for=20
others.</BLOCKQUOTE>HTH, <BR> Phill W. =
<BR> =20
<BR> </BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0010_01BEF9F9.2995AB00--
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads