Setting cursor to end of text (Access 2000)

Topic

New Reply

Hello all,

I have an access form with a large textbox (Reason_for_Change) on it so that when a user clicks on it their username (captured at login) and the current data/time appears, appended to whatever is already in the text box. That much of the code I have figured out:

Reason_for_Change.Value = Reason_for_Change.Value & vbCrLf & vbCrLf & gstrUserID & ” ” & Now

But my problem is that it leaves the textbox (Reason_for_Change) with all of its text highlighted. I want it to add the login information and time to the end of the text that is already in the textbox and leave the cursor either at the end of the text or, even better, on the next line (without all the text in the textbox highlighted).

Any ideas?

Thanks in advance,

Amanda

Reply | Quote

Replies

Go to tools/options/keyboard tab. You can set the enter field behavior to go to end of field. This is a global setting so I’m not sure if this suits your needs. The only other thing I can think of is to use a Sendkeys statement to pas an to the control. I tend to shy away from Sendkeys if I can. Pass a to go to the next line.

Reply | Quote

Change your line to this:

Reason_for_Change.Value = Reason_for_Change.Value & vbCrLf & vbCrLf & gstrUserID & ” ” & Now & vbCrLf

Then add this line next:

Me.Reason_for_change.SelStart = Me.Reason_for_change.SelLength + 1

Reply | Quote

Worked like a charm! Thanks so much!!

Regards,

Amanda

Reply | Quote

Just some food for thought. Your design will create a memo field (presumably) that grows each time you change the record. In addition, the usual requirement is to see why the last change was made, so you have to go to the end of the field in your text box to see that, and then read backwards if you want to see what the previous reason was. We do it a bit differently, and write out a record each time a change is made so we have a change history. In doing it that way, we can force people to put in a text string of reasonable length, and can usually limit the data to a text field of 255 characters. Then we we display it we sort it in descending date order (the record contains a DateTime field and an ID field that form a primary key) so the user can read the info in a more friendly manner. I realize you may be committed to your approach, but the concepts might be useful next time around.

Reply | Quote

Wendell is correct in taht his approach is much more structured and far easier to maintain.

However, if you were to rearrange your statement:
Reason_for_Change.Value = Reason_for_Change.Value & vbCrLf & vbCrLf & gstrUserID & ” ” & Now & vbCrLf

to:
Reason_for_Change.Value = vbCrLf & vbCrLf & gstrUserID & ” ” & Now & vbCrLf & Reason_for_Change.Value

You would then get your latest Reason at the top of your memo field.
Just my 2 bobs worth.
HTH
Pat

Reply | Quote