Continuous Sub-Form

[Tophan]

Good afternoon and Happy New Year!

I am working on a hotel project and created a continuous form listing all the tasks that need to be completed for the guestrooms with a Yes/No field. Each room will have the same tasks. I would like this form to be a subform where the main form will have approx. 4 fields - the primary key/autonumber field which will link to the subform; a date field, floor level field and room number field.

I've been reading different articles on how to create a continuous sub-form but have had no luck. I'm hoping someone on this forum can direct me on how best to achieve this.

Thanks in advance for your assistance.

 

[Edgar_]

I suggest you post a sample database or at least a few screenshots of the database schema and the continuous form you created. Assuming things are correctly setup, you would link main and continuous form via master/child links, which is a setting found in the Data tab of your subform control.

 

[CJ_London]

Suspect the issue is something else since when you create a subform control, you specify your continuous form as the source object.

I’m guessing it is probably an issue with your tables and relationships

 

[Tophan]

Thanks - I'll check again. I'm at the beginning stages of the DB so it's not too late to make any corrections.

 

[mike60smart]

Thanks - I'll check again. I'm at the beginning stages of the DB so it's not too late to make any corrections.

Can you post a screenshot of your Relationships Diagram?

 

[MarkK]

but have had no luck.

Describe the actual problem, for instance...

• you take action A
• you observe outcome B
• outcome B is not acceptable because of criteria C

Using a pattern like that to describe a problem will improve your luck.

 

[Pat Hartman]

There is only a single form object in Access. It shows either one record or multiple records in either continuous or datasheet view. The single form object may be used to add/change/delete records. It may be used as a main form or a subform but there is only a single form object. The code in the form is referencing the current record. In the case of the single form view, that would be the record you are looking at. In the case of the multiple record views, it is the record that contains the cursor.

If you post your schema and tell us a little more, I may have a sample that will help you. You would need to define a table that has tasks. And another that has room types because, there really could be different tasks should there be different room types. Then a third table that connects tasks to a specific room type. Then in your AfterUpdate event for the subform that adds a room, you would run an append query that copies all the tasks for the room type for the room you just added and appends them to the RentedRoomTasks table. Now you will have a subform that shows all the tasks for a room with a field to check complete and another comment field so you can add comments about things that are broken or missing or whatever. Then you can create end of day reports to make sure that someone reviews the comments.