How can I get Access to stop selecting all the text in a text box??? (1 Viewer)

Alan White said:

The global Client setting for "Behavior Entering Field", may not always be maintained.

Click to expand...

Ain't THAT the truth !!!

You probably noticed that I have code in the Enter event, not only for this text box but for several others, which sets the selection start to 0 and length to 0. Access only started misbehaving for this one text box after I moved it from the main form to the 2nd page of the new tab control. The text boxes on the 1st page of the tab control have similar code and work fine.

Should I call your procedure from the Enter event procedure or somewhere else?

I'm a brand new Access user... so take what i say with a lot of skepticism. If i understand your problem, try this (i'm using Access 2010).
Go to File > Options > Client Settings > Behavior Entering Field and set to 'Go to Start of Field.

Thanks for jumping in. This has gotten to be a long thread, but if you look at my very first post you'll see this: "The Client Setting for behavior on entering field is go to start of field. That should eliminate my problem, but it doesn't." And in message #16 I said "The Client settings are to put an insertion point at the start of the field when a control is entered."

That that's in fact what happens in all the other text boxes. It just doesn't happen in this one that resides by itself on the 2nd page of a Tab Control. Thanks for trying to help.

Myrna,
Thank you for you reply.
I have shared in your frustrations trying to provide a good user interface. Persistance has its own reward. I am not sure if you have solved your problem yet.

Private Sub Notes_Enter()
'Notes is the only control on the 2nd tab, i.e. Page 1
With Me.Notes
.SelStart = 0
.SelLength = 0
End With
Application.SetOption "Behavior Entering Field", 1 ' 1 = Start 2= End 0 = all
End Sub

I believe this should work.
Please let me know if it does...
Regards,
Alan

Sorry, but no, this didn't work. I'm not sure it should. You added the line to the Notes_Enter event sub. I believe (but am not sure) that this code runs AFTER the field has been entered, at which point the selection has already been made.

FWIW, in playing around with this, I created 2 more event procedures: (1) DoHip_LostFocus (that's the last field on the 1st page of the Tab Control), which sets focus to the Notes control and tries to set Notes' selection start and length, and (2) Notes_GotFocus, which also set selection start and length. Neither of these worked.

So I put break points in the code to see in what order the procedures ran, and I found that Notes_GotFocus ran BEFORE DoHip_LostFocus.

That seems strange to me, but perhaps there's no way to know one control has lost focus until you get the signal that a different control has received it. Since the sequence in which the code ran was consistent, I removed from DoHip_LostFocus the lines that set selection start and length -- Notes_Enter had already executed those instructions. But I had to retain the line that sets focus to Notes. Without it, tabbing out of DoHip moves to the next record!!

Another FWIW: if from the last text box on page 1 (DoHip) I press CONTROL+TAB to move to the 1st control on the 2nd tab (Notes), the selection is correct -- just an insertion point at the beginning.

Thanks for your input. BTW, if you download the sterilized file attached to a previous message, you also can try your code. Maybe you can get it to work.

At this point, I can only conclude that this is a bug. Oh, sorry, an issue.

I wonder if this issue has been resolved. it's awfully easy to delete a whole field of text when it is automatically selected.

threni said:

I wonder if this issue has been resolved. it's awfully easy to delete a whole field of text when it is automatically selected.

Click to expand...

Hi. There could be something wrong with the OP's file, which I didn't try, by the way, but when I did the following on my own ACCDB file, it worked as advertised. Have you tried it and still having problems with it? Or did you have a different problem altogether?

threni said:

I wonder if this issue has been resolved. it's awfully easy to delete a whole field of text when it is automatically selected.

Click to expand...

It has been over 7 years, chances are that it has. D

Maybe it has been solved, maybe not. I am aware of the length of time that has elapsed since the posting. Thanks to the dbGuy for offering a solution.