Multiple Forms for one table

[Famfeld]

Hi,
I am interested in creating 1 table and having multiple forms write to it but in a sequential way. The first form will fill out several fields, then another form will populate and show only the records that the first form entered but be able to add some additional fields. Once the second form decides that the record is complete, then that record will not be available for the first form. This may work better using queries, but I'm pretty new to this so please consider that. The design of this is similar to a checklist where user one creates a record and checks off some fields, then a second user would continue the record by checking off some different fields and then the record is deemed complete.



Any help appreciated.

Thank you,

Famfeld

[Micron]

Sounds like you've designed this table as you would a spreadsheet. What you're asking for doesn't make sense for a database. Can you elaborate on what the table looks like? Maybe a pic would save you a lot of explaining the table itself. Some info about what the table is about might help if the pic doesn't make that obvious.

[Famfeld]

Think of this like an assembly line where people are doing different jobs on the same records. One person enters a few fields and the next person enters a few different fields. Separate or the same form could be used, but I think it's easier to use separate and specific forms.

I don't have any photos yet.

Hope this helps some.

Famfeld

[CJ_London]

usual method is to create a single form and then use code to hide/disable/rearrange controls as necessary depending on the functionality required for each 'stage'. Means there is a lot less to maintain (although perhaps a little bit more work to get it done) and making changes only has to be done in one form, not several.

[Famfeld]

Thanks for the help

[ArviLaanemets]

In case working with DB will slow down because there is too many controls in forms totally, and too many of code in forms/controls events, you can consider having separate DB's for every workplace (or group of workplaces)/stage.

NB! Splitting a single form with lot of controls down to several smaller forms in same DB never doesn't make the DB faster - rather contrary, as total number of controls increases because some of them are mirrored in different forms. I think only valid reason to do this is with continous form, when you can't put all needed fields into max reasonable width of form. I had a design, where on 1st page of tab control was continuous form, and on 2nd page in single form were displayed comments for active row in 1st page form.

[Micron]

If I use your example, then as I envision it, there is one form, possibly one table for a 'job' and another for a list of tasks specific to that job.
I open a form and enter data that indicates my tasks are complete; each task and its details are a record in another table (junction table) - there is not a field for each task.
You open same form later and f'rinstance, a) see my completion details and all tasks, or b) only see your tasks or c) see only all uncompleted tasks or d) something else.
You complete your task details, creating records as did I. Ditto for everyone else. This is what I think you have designed and you're wondering if a 2nd form is the way to complete items 4 through 6, but maybe I'm wrong:

JobName	Task1	Task2	Task3	Task4	Task5	Task6
Fix it	....Y	....Y	....Y

[orange]

famfeld,

You may get some ideas from this Richard Rost youtube video on Tasks.