DayBackForFileMaker

Separation

DayBackForFileMaker.Separation History

Hide minor edits - Show changes to output

November 13, 2017, at 07:02 PM by 192.88.134.15 -
Changed line 11 from:
In a separated system you'll need to make a change to the way we handle colors in the event's record: [[separation colors | separated colors]].
to:
In a separated system you'll need to make a change to the way we handle colors in the event's record: [[separation colors | separatation colors]].
Changed lines 7-9 from:
Calendar Rows makes use of global variables that are declared in scripts in the interface file. And since global variables are scoped to the file, CalendarRows should be in the interface file, not the data file. Even though it has "records", they are really interface records, not data records. 

I'd say the same for the calendar interface table.
CalendarColors, however, belongs in your data file.
to:
"CalendarInterface" makes use of global variables that are declared in scripts in the interface file. And since global variables are scoped to the file, "CalendarInterface" should be in the interface file, not the data file.

CalendarColors,
however, belongs in your data file.
April 18, 2013, at 08:54 PM by 83.218.158.166 -
Changed lines 11-14 from:



to:
In a separated system you'll need to make a change to the way we handle colors in the event's record: [[separation colors | separated colors]].



June 10, 2010, at 10:58 AM by 166.137.9.54 -
Added lines 1-14:
!! Can I separate the calendar into Interface and Data files?

Definitely.

The only thing to remember is that a couple of the calendar tables belong in the interface file, not the data file.

Calendar Rows makes use of global variables that are declared in scripts in the interface file. And since global variables are scoped to the file, CalendarRows should be in the interface file, not the data file. Even though it has "records", they are really interface records, not data records. 

I'd say the same for the calendar interface table. CalendarColors, however, belongs in your data file.




(855) SEEDCODE
[email protected]
Follow us: