G'day ppl,
Here's what I would like to achieve.
In a continuous form setup:
Both cmbDepartFrom & cmbArriveAt have |NotInList| , |LimitToList=Yes| &
|AutoCap Function|
Lets assume:-
Record1
UserInput: cmbDepartFrom = Yard
UserInput: cmbArriveAt = National Rail
I would like the next record like this:
Record2
AutoPopulate: cmbDepartFrom = National Rail
UserInput: cmbArriveAt = Yard
Record3
AutoPopulate: cmbDepartFrom = Yard
UserInput: cmbArriveAt = Wharf
Record4
AutoPopulate: cmbDepartFrom = Wharf
UserInput: cmbArriveAt = Yard
Etc, Etc, & So On..............
I will also include an intResponse to cancel event should the user not want
to copy the value across.
This is a runsheet/log of "Departing From" & "Arriving At" locations for
drivers, hopefully will speed the data entry process where the user doesn't
have to repeat the input value
I look forward to your thoughts
TIA
Mark.
Marshall Barton - 07 Dec 2005 19:08 GMT
>Here's what I would like to achieve.
>
[quoted text clipped - 31 lines]
>drivers, hopefully will speed the data entry process where the user doesn't
>have to repeat the input value
I think this is easier than what you're asking about with a
BeforeUpdate event (which I don't see how that might be
done).
Try just using the arrive combo box's AfterUpdate event to
set the depart combo box's DefaultValue property:
Me.cmbDepartFrom.DefaultValue = """" & Me.cmbArriveAt & """"
If the user doesn't like the automatically supplied value,
they can just type in a new value in the usual way. No
button needed.

Signature
Marsh
MVP [MS Access]
NoodNutt - 09 Dec 2005 06:14 GMT
G'Day Marshall,
DOH!, you're absolutely so spot on with your assessment, way too many late
nights for me, and definitely not enough bourbon me thinks.
Thx again.
Mark.
>>Here's what I would like to achieve.
>>
[quoted text clipped - 46 lines]
> they can just type in a new value in the usual way. No
> button needed.