If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
Where the cursor starts after clicking no a text box
Wish we could edit here! Meant to emphasize that the last part
"As I stated earlier, I think his problem is because the fields are numerical, and so the "start" of the field is the right hand side of the textbox, not the left hand side, as it is for text fields." is just a guess! Perhaps it is an SP3 gotcha! God knows there are plenty of them out there! -- There's ALWAYS more than one way to skin a cat! Answers/posts based on Access 2000/2003 Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/200801/1 |
#12
|
|||
|
|||
Where the cursor starts after clicking no a text box
Placing the code in the
GotFocus event will have no effect when the textbox is entered by way of clicking with the mouse Sorry, that is not correct. I just did a test on that and clicking in the text box does fire the Got Focus event. -- Dave Hargis, Microsoft Access MVP "Linq Adams via AccessMonster.com" wrote: Klatuu: "Second, the click event will not fire every time you enter the control. The code should be in the GotFocus Event." Actually, you right and you're wrong, Klatuu! Placing the code in the GotFocus event will have no effect when the textbox is entered by way of clicking with the mouse! It doesn't make a lot of dince, but we're talking about Access here! I know this because I've been using this type of code since ACC2000. It does have to be placed in GotFocus as well, ***unless*** in Options.- Keyboard - Behavior Entering Field the option is set to "Go to start of field." As I stated earlier, I think his problem is because the fields are numerical, and so the "start" of the field is the right hand side of the textbox, not the left hand side, as it is for text fields. -- There's ALWAYS more than one way to skin a cat! Answers/posts based on Access 2000/2003 Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/200801/1 |
#13
|
|||
|
|||
Where the cursor starts after clicking no a text box
What version of Access are you running? It certainly doesn't in
Access2000/2003! Select a textbox and place this code behind it: Private Sub TextBoxName_GotFocus() MsgBox "Clicking caused GotFocus to fire!" End Sub Run the form and click on the textbox; no messagebox appears! -- There's ALWAYS more than one way to skin a cat! Answers/posts based on Access 2000/2003 Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/200801/1 |
#14
|
|||
|
|||
Where the cursor starts after clicking no a text box
I can't comment on what version Dave's using, but I get the message box in
Access 97. You sure the text box's On Got Focus property is set to [Event Procedure]? -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) "Linq Adams via AccessMonster.com" u28780@uwe wrote in message news:7ddbb270ede98@uwe... What version of Access are you running? It certainly doesn't in Access2000/2003! Select a textbox and place this code behind it: Private Sub TextBoxName_GotFocus() MsgBox "Clicking caused GotFocus to fire!" End Sub Run the form and click on the textbox; no messagebox appears! |
#15
|
|||
|
|||
Where the cursor starts after clicking no a text box
Access 2003 SP3, XP Pro.
When I said I had tested it, that is exactly what I did. The message box appears when I click on the text box. -- Dave Hargis, Microsoft Access MVP "Linq Adams via AccessMonster.com" wrote: What version of Access are you running? It certainly doesn't in Access2000/2003! Select a textbox and place this code behind it: Private Sub TextBoxName_GotFocus() MsgBox "Clicking caused GotFocus to fire!" End Sub Run the form and click on the textbox; no messagebox appears! -- There's ALWAYS more than one way to skin a cat! Answers/posts based on Access 2000/2003 Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/200801/1 |
#16
|
|||
|
|||
Where the cursor starts after clicking no a text box
Access 2003 SP3, XP Pro.
I have used a simiar technique since Ac97 and the GotFocus always fires when you click on the text box. -- Dave Hargis, Microsoft Access MVP "Douglas J. Steele" wrote: I can't comment on what version Dave's using, but I get the message box in Access 97. You sure the text box's On Got Focus property is set to [Event Procedure]? -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) "Linq Adams via AccessMonster.com" u28780@uwe wrote in message news:7ddbb270ede98@uwe... What version of Access are you running? It certainly doesn't in Access2000/2003! Select a textbox and place this code behind it: Private Sub TextBoxName_GotFocus() MsgBox "Clicking caused GotFocus to fire!" End Sub Run the form and click on the textbox; no messagebox appears! |
#17
|
|||
|
|||
Where the cursor starts after clicking no a text box
Curiouser and curiouser!
"You sure the text box's On Got Focus property is set to [Event Procedure]?" Yes, I always go to the code window thru the Property Box for whatever event I'm coding, so it's set to [Event Procedure]. Also, I just went back and ran up a form from scratch, placed a textbox on it, and did the same thing as above, with the same (for me) negative results. GotFocus didn't fire. Actually, I did all of this TWICE! Once on my box, running Access 2003, and I had a friend here with a laptop running Access 2000, same results on his machine! As John Walton use to say "Life's a mystery!" -- There's ALWAYS more than one way to skin a cat! Answers/posts based on Access 2000/2003 Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/200801/1 |
|
Thread Tools | |
Display Modes | |
|
|