the "payperiod" is a field in the table that both forms use. there
will be data present in the timesheetlaunch form but not present in
the form we are going to until we move it. I don't think the record
is saving when the button is clicked so maybe that is part of the
problem?
payperiod data is structured as date/time
the last question about the error. it is popping the error when the
form opens. if i just use the form by itself without clicking the
button to get to it is the same.
Ken Snell (MVP) - 28 Jun 2008 22:57 GMT
I am traveling for work, which is delaying my reply to your post. I'll post
as soon as I can.

Signature
Ken Snell
<MS ACCESS MVP>
> the "payperiod" is a field in the table that both forms use. there
> will be data present in the timesheetlaunch form but not present in
[quoted text clipped - 7 lines]
> form opens. if i just use the form by itself without clicking the
> button to get to it is the same.
Ken Snell (MVP) - 01 Jul 2008 03:16 GMT
Am I understanding correctly? You're entering a value for the payperiod on
the form and then clicking the button to carry that value to the second
form? Where on the form is the button located -- in which section of the
form? Is the form on which you're entering the payperiod data a continuous
forms view or single forms view?
What is the name of the form's control that holds the entered payperiod
value?
It would appear to me that the form cannot "see" the data value and thus is
not able to carry it to the other form. Please provide as much detail about
the form and what you do on the form before clicking the button.

Signature
Ken Snell
<MS ACCESS MVP>
> the "payperiod" is a field in the table that both forms use. there
> will be data present in the timesheetlaunch form but not present in
[quoted text clipped - 7 lines]
> form opens. if i just use the form by itself without clicking the
> button to get to it is the same.