![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
#12
| |||
| |||
|
|
Ugh, I knew I was going to wind up asking too many questions, but which side is considered the "parent" side? The NOAA 2 table occurance. |
#13
| |||
| |||
|
#14
| |||
| |||
|
|
That seems to have done it! I won't even bother wondering why it seemed to sort of work before with the wrong boxes checked. Followup question: in terms of the incrementation of the ProjectID field, I noticed that all the tasks associated with one record have the same ProjectID (which I expected), but the next record's ProjectID isn't an increase of 1; it's usually an increase of 2 or 3. I thought perhaps the numeric increase was related to how many tasks I created, but that doesn't seem to be the case... That is because you have the ProjectID field in the "tasks" table setup |
#15
| |||
| |||
|
#16
| |||
| |||
|
|
Last question (I promise!): how would I create a separate layout that would display Institution, TaskType, TaskDescription, and ProjectID for each task created in the other layout? I want to make sure that the info is properly getting into the Tasks table... I tried just creating a layout that uses data from the Tasks table and displays these fields (with the "institution" field coming from NOAA 2) but that didn't seem to work. Thanks again for your quick and patient replies! Cheers, John |
#17
| |||
| |||
|
|
And i'm intrigued by the field one < calculated , number ; 1 > What is it's purpose? Why a calculation to a constant one? And not in use anywhere else.. These thing make me wonder.... |
![]() |
| Thread Tools | |
| Display Modes | |
| |