If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Control limitations
G'day all
Using Acc2003 in 2K format, as work has not taken the step up to 2007 yet. Is there a way to bypass the maximum "Controls on/in a form" limitation. Background: Essentially, I am attempting to create a "Fatigue Management" DB which records all driver activities during each 24 hour period over a seven day period. The particular form I am attempting to generate requires a substantial amount of input as it is based over a 24 hour period broken into 15 minute increments. Each 15 minute incremented bracket contains the following control: 1 x Option frame with 2 options (Rest or Work) 2 x Labels which change colour depending on selection 6 x Lines for seperation 1 x control source field Multiply this by 24 hours and there is lots, so far I have got to 7 hours and I have hit the wall, and the above still does not include the actual time calculation fields which will have to be done via 2 seperate subforms due to this control limitation issue. I look forward to any suggestions TIA Mark. |
#2
|
|||
|
|||
Control limitations
Sounds like a non-normalized design. Each 15 minute increment is the
smallest chunk you need to record information about, so would that not be the lowest child on the relationships? If you build that first, you can drop it into a Person/Date form... but if you're trying to do this as if it were a spreadsheet, you need to rethink your design. Before you even start the interface, try adding a few records to your tables and getting the correct query results. If you don't, you run the risk of coming up with an interface that appears to work, but underlying table structures that do not allow you to effectively query the data you have collected. -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/201005/1 |
#3
|
|||
|
|||
Control limitations
Thx for your reply Pieter
I was kinda hoping to make it Point/Click with the layout, seems it won't be, so it's back to the drawingboard. Thx again. "PieterLinden via AccessMonster.com" u49887@uwe wrote in message news:a880fef18b146@uwe... Sounds like a non-normalized design. Each 15 minute increment is the smallest chunk you need to record information about, so would that not be the lowest child on the relationships? If you build that first, you can drop it into a Person/Date form... but if you're trying to do this as if it were a spreadsheet, you need to rethink your design. Before you even start the interface, try adding a few records to your tables and getting the correct query results. If you don't, you run the risk of coming up with an interface that appears to work, but underlying table structures that do not allow you to effectively query the data you have collected. -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/201005/1 |
Thread Tools | |
Display Modes | |
|
|