YET ANOTHER ANOMALY...CARRYING FORWARD DATA

[Rich_Lovina]

I'm using the following code so the user does not re-type same info:
In After_Update,
Me![Deptcode].Tag = Me![Deptcode].Value
And in On_Enter,
If Not (IsNull(Me![Deptcode].Tag) Or Me![Deptcode].Tag = "") Then
Me![Deptcode].Value = Me![Deptcode].Tag
End If

This code is fine except when the form is opened and one record is edited, then if scrolling back or forwards the last edited correction goes and changes all the previously entered texts. I solved this last year but have forgotten what it was.

 

[Rich_Lovina]

Whoops...Have just found Knowledge Base article which uses AutoFillNewRecord function, as way to go, NOT the above which presents the anomaly.

 

[David R]

What about Control-'? It's admittedly low-tech, but it usually works in a pinch for situations where the data is only the same by virtue of when it's entered, not because you're duplicating data.

David R

 

[Rich_Lovina]

David, not quite sure what you mean, plus for high speed data-entry user having to press Ctrl plus another key, gets their fingers in a bind. They just want keyboard and Tabkey to do the job....no mice and no two keys at once.

 

[David R]

Gotcha. I "only" type 90 wpm so using Ctrl-' works just fine for me.

Cheers,
David R

 

[Rich_Lovina]

Yeh but my data-enterer does 19,500 keystrokes per hour, which is as you may know, 5.4 strokes per second....no time to move to control!!!