Have Data Input Design Problem - STUMPED!

[rpeare]

ug... if there is a recordsource I forgot to remove it, what I typically do is make the record source whatever table I'm working with at the moment to make control names have the correct ones when I add a load of controls to the form, then I remove the record source after the fields are added.



the form FRMJOB should not have a record source, when you open it you can delete what it currently says ("TBLWORKDATE")

thanks for pointing it out june

[rpeare]

oop and as to version, I'm limited in my version by location which varies, the lowest of which is 2003 when they upgrade to something higher I'll update it, I promise.

[Micron]

Moderator and rpeare: I changed my profile. Until I came here this week, I had forgotten that I was even registered. In my defense, the version was specified in my first post. I have been able to open the new link and took a quick look but have run out of time today and will not be in on Friday (funeral). If I don't reply tomorrow, I'll shoot for Monday. In the meantime, I created a gif of what I thought user would see as inputs or edits (ignore the colours - just there to define the areas a bit). Note: in my example, this job only lasted 5 days. Not necessarily will always be the case. If your db sample is not conducive to the goal, please let me know so I don't take too much time exploring your db. Thanks!

[Micron]

Attachment 19674

Try this

This is an unbound form (I don't use bound forms)

Your example provided a solution to table reforms and design for new ones. Not sure this will be clear to you, but the links are: tblAllWork.ID > tblWrkDteDtl.ID > tblWrkDteTrade.ID > tblTrades.ID. As for the input solution, I'm going with a continuous form and a temp table into which I can easily insert n rows of dates based on the #of days in any month. This will give me an input form with the right number of data entry rows which is based on a volatile number. Using the appropriate ID field in the temp, I should be able to insert or update data into the main table. I guess I will have to test if the job ID exists in the work date detail table to know whether or not the form should open in data entry or update mode for that job. It will drive whether or not the sql says INSERT INTO or UPDATE.
Many thanks to you guys for your assistance.