yes, but - realize that both forms must be open. Form2 will be open, - but form1 needs to be open also, otherwise the reference will not provide the value, but will cause problems.
EscapeUK wants an 'easy' way to do it - not a possible way to do it.
Several 'things' need to be calriified/understood before the 'easy way' can be given.
Perhaps the easy way would be to set the transfer up to not have 'problems' to begin with.Some assumptions here which are necessary because EscapeUK did not provide much information:
[tab]Form2 is NOT the startup form.
[tab]
In the startup object, reference some general (public) module.
In the referenced general module, decalre a public (or global) variable (I'll call it txtToXfer).
In the startup object, set txtToXfer to some general value which would at least NOT cause a problem when used in Form2. This could be a value which, while it does not ause an error, is never a valid value for the transfer. If this is done, Form2 could check for the invalid value and 'know' there was a problem.
In Form1, the control which has the value to be 'transfered' to elsewhere (e.g. Form2) whenever it is changed should set the value of [txtToXfer] to it's own value.
If Form2, set the controlsource of the control which uses/dispalys the transfered value to txtToXfer.
MichaelRed
redmsp@erols.com
There is never time to do it right but there is always time to do it over