multiple dates needed for subform--service orders

[Guest]

I need to enter data into several 'date' fields in a subform--time in and out
on several days. It will accept the time but will change the dates back to
the opening date from the main form. Properties in the 'date' field on the
subform show its control to be 'Date' from the subform field list. How do I
make it accept many dates and employee hours for one service record?

 

[John Vinson]

I need to enter data into several 'date' fields in a subform--time in and out
on several days. It will accept the time but will change the dates back to
the opening date from the main form. Properties in the 'date' field on the
subform show its control to be 'Date' from the subform field list. How do I
make it accept many dates and employee hours for one service record?

Could you describe your table structure? What's the Main form's
Recordsource? The Subform's? Do you actually have a field named Date -
note that it's a reserved word and a dangerous choice of fieldname!

Bear in mind that Forms *are only windows*. They do not contain any
data. The table contains data; the form lets you view and edit that
data.

John W. Vinson[MVP]

 

[Guest]

The table structure is relatively simplistic; fields for service call info,
employee total time on service order and total amount of parts used, repairs
done, etc. (Is that what you mean by structure?). The main form's record
source is the table and the sub form's is also the table with some
independant fields specific to the subform only. However, the subform is a
detail of parts used and time in and time out per employee per day, so there
can be multiple days spent by several employees on a particular service
order. Right now the subform alows me to enter all these dates, etc., but
wipes them out as soon as I leave that record. I wish I could show you a
screen shot and it might make it more clear.

Thank you so much for your help with this. I'm flying kinda blind here.

 

[John Vinson]

The table structure is relatively simplistic; fields for service call info,
employee total time on service order and total amount of parts used, repairs
done, etc. (Is that what you mean by structure?). The main form's record
source is the table and the sub form's is also the table with some
independant fields specific to the subform only. However, the subform is a
detail of parts used and time in and time out per employee per day, so there
can be multiple days spent by several employees on a particular service
order. Right now the subform alows me to enter all these dates, etc., but
wipes them out as soon as I leave that record. I wish I could show you a
screen shot and it might make it more clear.

Thank you so much for your help with this. I'm flying kinda blind here.

What would make it more clear is for you to post the Recordsource
properties of the mainform and the subform, as requested.

If the "independent fields specific to the subform only" are unbound
textboxes on the subform, then any information typed into those
controls will indeed be lost. It seems you're still in the mindset
that data is stored somehow IN A FORM. *It isn't*. Forms to NOT
contain or retain data; they're windows which are used to display data
stored in Tables.

John W. Vinson[MVP]

 

[Guest]

Wow. That helped alot.

What would make it more clear is for you to post the Recordsource
properties of the mainform and the subform, as requested.

If the "independent fields specific to the subform only" are unbound
textboxes on the subform, then any information typed into those
controls will indeed be lost. It seems you're still in the mindset
that data is stored somehow IN A FORM. *It isn't*. Forms to NOT
contain or retain data; they're windows which are used to display data
stored in Tables.

John W. Vinson[MVP]

 

[John Vinson]

Wow. That helped alot.

Informative question only, not a criticism:

was this actually helpful? or were you being sarcastic?

I realize that I didn't solve your problem (can't, because I don't
have the needed information), so I'm not sure if you need more advice
or not!

John W. Vinson[MVP]