![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello All I have been googling, trying to find a sample of a form where list boxes are used based for a fairly complex schedule and multiple resource locations. There will be approximately 100 "locations" within in 10 sections on the form. *Instructors are assigned to a section and students to each location (average 2 per location) - these will only load if records exist in a schedule table/query, I also want to drill down and edit underlying data. *Ideally I would set up the locations as hidden on an unbound blank canvas/form and If anyone has designed such a beast or can share some ides, I would very much appreciate some tips. many thanks John |
#3
| |||
| |||
|
|
On Jun 1, 5:57*pm, flymo <fly... (AT) hotmail (DOT) com> wrote: Hello All I have been googling, trying to find a sample of a form where list boxes are used based for a fairly complex schedule and multiple resource locations. There will be approximately 100 "locations" within in 10 sections on the form. *Instructors are assigned to a section and students to each location (average 2 per location) - these will only load if records exist in a schedule table/query, I also want to drill down and edit underlying data. *Ideally I would set up the locations as hidden on an unbound blank canvas/form and If anyone has designed such a beast or can share some ides, I would very much appreciate some tips. many thanks John Hi John, I worked on a couple of those beasts, but every beast is a different beast. So it has no sense to give an example, but sharing ideas is a possibility. But on this moment I do not understand the use of listboxes. Why do you think you need them? Imb. |
#4
| |||
| |||
|
|
Hello lmb I was investigating setting up calendar forms a few weeks ago and the most used item were unbound listboxes, so seemed to be a good starting point. *If there is a more usable format I am interested in learning. John- Hide quoted text - - Show quoted text - |
#5
| |||
| |||
|
|
Hello lmb I was investigating setting up calendar forms a few weeks ago and the most used item were unbound listboxes, so seemed to be a good starting point. *If there is a more usable format I am interested in learning. John- Hide quoted text - - Show quoted text - Hi John, What a more usable format is depends very much on your way of working and the used systematics. At least my approach works great for me. I will try to explain my way of working. I am not focussed on list boxes, because I never use these. I have a “layout form” with many unbound hidden controls. This layout- form can be used for areal layouts, such as a floor plan, but also for time slots for planning/scheduling purposes. In the On_open event of the form a procedure is run in which all necessary controls are made visible and get their right dimensions and positions. In case of time slots the positons can be calculated given the dimensions, whereas in the case of a floor plan I pick up the dimensions and positions from a definition table. During this processing I build up a string – if necessary – to keep track of the relation between time slot or “floor item” and the used control. The next part of the openings procedure is to fill in the appropriate data. I loop through the appropriate set. I know exactly which controls on the form must be modified in terms of text, colour, or whatever. The current record ID is stored in the Tag of the control. Doubleclicking the controls leads you to the procedure where is analysed what has to be done. In case of a filled Tag a “single record form” is opened with all the details of the record with that ID that – depending on the authorisation level – can be modified. In case of a not-filled Tag a “new record form” is opened. After a change in the underlying data the openingsprocedure is run again to refresh the form. It is also possible to delete or disable the underlying record, to wipe it out from the form (this is not the same as just empty the Tag of the control). On the form you can have navigation buttons to change the time definition of the time slots, or in case of a floor plan, how the plan will look tomorrow or looked last week. I can imagine this all looks complicated, and perhaps I forgot to mention some steps that are trivial for me but essential for your understanding, but I will be glad to explain this further. Imb. |
#6
| |||
| |||
|
|
lmb Thanks for taking time to break that down, it sounds very much like what I am aiming for, certainly going in the right direction. A static floor layout based on an instructor with X # students (value based on a table setting which varies per instructor e.g. 7 students) scheduled within a geographical area on the floor plan and a max of 2 (# students per bench) records within each unbound "cell", either/each/ both of which can be edited/deleted. The details can change daily depending on date. I am very interested in hearing more, here or on an email/chat basis. Thanks again John |
#7
| |||
| |||
|
|
lmb Thanks for taking time to break that down, it sounds very much like what I am aiming for, certainly going in the right direction. A static floor layout based on an instructor with X # students (value based on a table setting which varies per instructor e.g. 7 students) scheduled within a geographical area on the floor plan and a max of 2 (# students per bench) records within each unbound "cell", either/each/ both of which can be edited/deleted. The details can change daily depending on date. I am very interested in hearing more, here or on an email/chat basis. Thanks again John Hi John, I assume your basic data is written (normalized) in some Attendee_tbl, that describes which students attend which course in that area. Fields in this table are for instance: - Course_id: FK to Course_tbl, that holds the courses, including a reference to the instructor, - Person_id: FK to Person_tbl, that holds all the personal information of the students, - Tablenumber. So the recordset for one room contains all the Persons that follow the Course with Id = Course_id. Further, each bench in the area consists of two unbound controls, so that each control contains exactly one Person, or contains an empty place. I do not know the names you use for tables and fields, but this should give you a start. Imb. |
![]() |
| Thread Tools | |
| Display Modes | |
| |