DayBackOnline

Integrating DayBack with Your FileMaker File(s)

DayBackOnline.Integration History

Hide minor edits - Show changes to output

July 15, 2015, at 04:53 PM by 142.4.217.188 -
Changed line 7 from:
(:youtube z_u-m79pG9E width=500:)
to:
(:youtube 8i46vj7WfP0 width=500:)
July 01, 2015, at 02:25 PM by 142.4.217.188 -
Changed lines 11-17 from:
!! Logging in as an admin

If you created your own DayBack Online account you're already an administrator and clicking on "Settings" in the calendar's left hand side bar will reveal an "Administrator Settings" button that will let you configure sources.

If you're logging in to our demo using "demo@dayback.com" you're not an admin of that account and won't be able to configure a the FileMaker connection there. (We wouldn't want you publishing your FileMaker events to all our demo users.
) You can create your own account here: https://beta.dayback.com/#/sign-up

Finally, if someone invited you to join their DayBack group they can decide to make you an admin of the group or not: ask them nicely.
to:
(:include Administrators:)
July 01, 2015, at 02:23 PM by 142.4.217.188 -
Added lines 22-23:

%newwin, width=500% [[https://www.seedcode.com/rootimages/stikipad/daybackonline/SourceSettings.png | https://www.seedcode.com/rootimages/stikipad/daybackonline/SourceSettings.png]]
July 01, 2015, at 02:01 PM by 142.4.217.188 -
Added lines 20-25:

Once you arrive at Admin Settings, you'll see "Calendar Sources" in the left hand side bar. Click "FileMaker Server" and then the button to add a new source (you can also edit an existing source if one is already there).

Follow the instructions in the right half of the screen and you'll be up and running shortly. Please [[https://www.seedcode.com/contact/ | get in touch]] if you have questions.

Thanks!
July 01, 2015, at 01:57 PM by 142.4.217.187 -
Added lines 3-4:
!! Overview
Added lines 11-19:
!! Logging in as an admin

If you created your own DayBack Online account you're already an administrator and clicking on "Settings" in the calendar's left hand side bar will reveal an "Administrator Settings" button that will let you configure sources.

If you're logging in to our demo using "demo@dayback.com" you're not an admin of that account and won't be able to configure a the FileMaker connection there. (We wouldn't want you publishing your FileMaker events to all our demo users.) You can create your own account here: https://beta.dayback.com/#/sign-up

Finally, if someone invited you to join their DayBack group they can decide to make you an admin of the group or not: ask them nicely.

!! Configuring your FileMaker table as a calendar source
July 01, 2015, at 01:50 PM by 142.4.217.188 -
Added lines 4-5:

(:youtube z_u-m79pG9E width=500:)
July 01, 2015, at 01:49 PM by 142.4.217.188 -
Changed lines 3-17 from:
!! Two Options: Linking and Embedding

There are two ways to get the calendar to work with your file. You can
'''link''' the calendar file to your, or you can '''embed''' it. Embedding means pasting the fields, scripts, and layouts required from our file into yours. Linking means that the calendar would continue to run as a separate file, but would use your file for the calendar data.

'''Linking''' the two files is '''by far''' the easiest approach and if you often want to see the calendar in its own window then this is definitely the way to go. This is also the best option for folks who are newer to FileMaker.

One downside to a linked file is that, like all multi-file solutions, you'll need to have your accounts and privilege sets in both files (unless you set the calendar file to auto-open with its own, low access password for everyone
)-- that's the only downside of linking And if you're using %newwin% [[https://www.filemaker.com/12help/html/passwords.14.13.html | external authentication]], then it's no downside at all.

-> Learn how to [[Quick Integration | Link the Calendar]].

'''Embedding''' the calendar into your file means the calendar ends up as a layout (its own layout, not part of an existing layout) in your file so you'll discard our example file when you're done. This is a more tedious integration process but if you follow our instructions carefully it doesn't take that long.

-> Learn how to [[Embedding The Calendar | Embed the Calendar]].

(:include NeedHelp:)
to:
Configuring DayBack Online to work with your FileMaker Server is done almost entirely by filing out a form in DayBack's settings screen. If you're using DayBack for FileMaker you already have the required FileMaker fields and layouts and this will go very quickly: see what we mean in this quick video:

If you're using another FileMaker
file, the settings form will describe a couple of fields you'll need to add to your FileMaker table, as well as a layout you'll add to your file. The video above is still a nice overview of what this entails =)
April 06, 2015, at 02:27 PM by 142.4.217.188 -
Changed lines 17-23 from:
!! Need Help?

Our products are designed so you can integrate them into your own FileMaker solutions yourself following the instructions in our online documentation, and our team is happy to provide any guidance you need at no additional charge. So please don't hesitate to [[https
://www.seedcode.com/contact/ | reach out]] if you get stuck--we can likely get your integration unstuck with a quick phone call or email.

Alternatively, our trained and certified developers can do your integration for you from start to finish. Just pick up our minimum three-hour [[https://www.seedcode.com/implementation-packages/ | implementation package]] ($570
) and send us your file (more complex integrations may require more time).

We can also help you build custom features in any FileMaker solution that involves one or more of our products, including customized deployments of [[https://www.seedcode.com/complete-filemaker-template/ | SeedCode Complete]]. For these types of projects that involve custom-built features, please [[https://www.seedcode.com/contact/ | get in touch]] to discuss the details so we can give you an estimate of the cost and timeline.
to:
(:include NeedHelp:)
April 06, 2015, at 02:20 PM by 142.4.217.188 -
Changed line 19 from:
Our products are designed so you can integrate them into your own FileMaker solutions yourself following the instructions in our online documentation, and our team is happy to provide any guidance you need at no additional charge. So please don't hesitate to [[https://www.seedcode.com/contact/ | get in touch]] if you get stuck--we can likely get your integration unstuck with a quick phone call or email.
to:
Our products are designed so you can integrate them into your own FileMaker solutions yourself following the instructions in our online documentation, and our team is happy to provide any guidance you need at no additional charge. So please don't hesitate to [[https://www.seedcode.com/contact/ | reach out]] if you get stuck--we can likely get your integration unstuck with a quick phone call or email.
April 06, 2015, at 02:20 PM by 142.4.217.188 -
Changed line 19 from:
Our products are designed so you can integrate them into your own FileMaker solutions yourself following the instructions in our online documentation, and our team is happy to provide any guidance you need at no additional charge.
to:
Our products are designed so you can integrate them into your own FileMaker solutions yourself following the instructions in our online documentation, and our team is happy to provide any guidance you need at no additional charge. So please don't hesitate to [[https://www.seedcode.com/contact/ | get in touch]] if you get stuck--we can likely get your integration unstuck with a quick phone call or email.
April 06, 2015, at 02:18 PM by 142.4.217.187 -
Changed lines 19-20 from:
Our products are designed so you can integrate them into your own FileMaker solutions yourself following the instructions in our online [[https://www.seedcode.com/pmwiki/ | documentation]], and our team is happy to provide any guidance you need at no additional charge.
to:
Our products are designed so you can integrate them into your own FileMaker solutions yourself following the instructions in our online documentation, and our team is happy to provide any guidance you need at no additional charge.
Changed line 23 from:
We can also build custom features in any FileMaker solution that involves one or more of our products, including customized deployments of [[https://www.seedcode.com/complete-filemaker-template/ | SeedCode Complete]]. For these types of projects that involve custom-built features, please [[https://www.seedcode.com/contact/ | get in touch]] to discuss the details so we can give you a cost and timeline estimate.
to:
We can also help you build custom features in any FileMaker solution that involves one or more of our products, including customized deployments of [[https://www.seedcode.com/complete-filemaker-template/ | SeedCode Complete]]. For these types of projects that involve custom-built features, please [[https://www.seedcode.com/contact/ | get in touch]] to discuss the details so we can give you an estimate of the cost and timeline.
April 03, 2015, at 04:13 PM by 142.4.217.188 -
Changed line 19 from:
Our products are designed so you can integrate them into your own FileMaker solutions yourself following the instructions in our online [[https://www.seedcode.com/implementation-packages/ | documentation]], and our team is happy to provide any guidance you need at no additional charge.
to:
Our products are designed so you can integrate them into your own FileMaker solutions yourself following the instructions in our online [[https://www.seedcode.com/pmwiki/ | documentation]], and our team is happy to provide any guidance you need at no additional charge.
April 03, 2015, at 04:12 PM by 142.4.217.188 -
Changed lines 19-23 from:
Please don't hesitate to [[https://www.seedcode.com/contact/ | get in touch]] if you get stuck--we can likely get you unstuck with a quick phone call or email. If you don't want to do the integration yourself, or would like to take things further than these docs describe, SeedCode can integrate this for you as part of an [[https://www.seedcode.com/implementation-packages/ | implementation package]].
to:
Our products are designed so you can integrate them into your own FileMaker solutions yourself following the instructions in our online [[https://www.seedcode.com/implementation-packages/ | documentation]], and our team is happy to provide any guidance you need at no additional charge.

Alternatively, our trained and certified developers
can do your integration for you from start to finish. Just pick up our minimum three-hour [[https://www.seedcode.com/implementation-packages/ | implementation package]] ($570) and send us your file (more complex integrations may require more time).

We can also build custom features in any FileMaker solution that involves one or more of our products, including customized deployments of [[https://www.seedcode.com/complete-filemaker-template/ | SeedCode Complete]]. For these types of projects that involve custom-built features, please [[https://www.seedcode.com/contact/ | get in touch]] to discuss the details so we can give you a cost and timeline estimate
.
Changed line 13 from:
'''Embedding''' the calendar into your file means the calendar ends up as a layout (it's own layout, not part of an existing layout) in your file so you'll discard our example file when you're done. This is a more tedious integration process but if you follow our instructions carefully it doesn't take that long.
to:
'''Embedding''' the calendar into your file means the calendar ends up as a layout (its own layout, not part of an existing layout) in your file so you'll discard our example file when you're done. This is a more tedious integration process but if you follow our instructions carefully it doesn't take that long.
Changed line 1 from:
(:title Integrating DayBack with Your File:)
to:
(:title Integrating DayBack with Your FileMaker File(s):)
Changed line 1 from:
(:include Integrating DayBack with Your File:)
to:
(:title Integrating DayBack with Your File:)
Added lines 1-2:
(:include Integrating DayBack with Your File:)
Changed lines 13-17 from:
-> Learn how to [[Embedding The Calendar | Embed the Calendar]].
to:
-> Learn how to [[Embedding The Calendar | Embed the Calendar]].

!! Need Help?

Please don't hesitate to [[https://www.seedcode.com/contact/ | get in touch]] if you get stuck--we can likely get you unstuck with a quick phone call or email. If you don't want to do the integration yourself, or would like to take things further than these docs describe, SeedCode can integrate this for you as part of an [[https://www.seedcode.com/implementation-packages/ | implementation package
]].
Deleted lines 0-1:
-> [++++"A man with two watches never knows what time it is."++++] - Chinese Proverb, (and a great reason to get all your events into one calendar).
Changed line 1 from:
-> [++++"A man with two watches never knows what time it is."++++] - Chinese Proverb, (and a great reason to get all your events in one calendar).
to:
-> [++++"A man with two watches never knows what time it is."++++] - Chinese Proverb, (and a great reason to get all your events into one calendar).
Changed line 1 from:
-> [+++"A man with two watches never knows what time it is."+++] - Chinese Proverb, (and a great reason to get all your events in one calendar).
to:
-> [++++"A man with two watches never knows what time it is."++++] - Chinese Proverb, (and a great reason to get all your events in one calendar).
Changed line 1 from:
-> [++"A man with two watches never knows what time it is."++] - Chinese Proverb, (and a great reason to get all your events in one calendar).
to:
-> [+++"A man with two watches never knows what time it is."+++] - Chinese Proverb, (and a great reason to get all your events in one calendar).
Changed lines 1-2 from:
 [++"A man with two watches never
knows what time it is."++] - Chinese Proverb, (and a great reason to get all your events in one calendar).
to:
-> [++"A man with two watches never knows what time it is."++] - Chinese Proverb, (and a great reason to get all your events in one calendar).
Changed lines 1-2 from:
 [++"A man with two watches never knows what time it is."++] - Chinese Proverb, (and a great reason to get all your events in one calendar).
to:
 [++"A man with two watches never
knows what time it is."++] - Chinese Proverb, (and a great reason to get all your events in one calendar).
Changed line 1 from:
>>"A man with two watches never knows what time it is." - Chinese Proverb, (and a great reason to get all your events in one calendar).<<
to:
 [++"A man with two watches never knows what time it is."++] - Chinese Proverb, (and a great reason to get all your events in one calendar).
Added lines 1-2:
>>"A man with two watches never knows what time it is." - Chinese Proverb, (and a great reason to get all your events in one calendar).<<
Changed lines 3-4 from:
There are two ways to get the calendar to work with your file. You can '''link''' the SeedCode Calendar file to your, or you can '''embed''' it, pasting the fields, scripts, and layouts required from our file into yours.
to:
There are two ways to get the calendar to work with your file. You can '''link''' the calendar file to your, or you can '''embed''' it. Embedding means pasting the fields, scripts, and layouts required from our file into yours. Linking means that the calendar would continue to run as a separate file, but would use your file for the calendar data.
Changed lines 7-10 from:
Like all multi-file solutions you'll need to have your accounts and privilege sets in both files (unless you set the calendar file to auto-open with its own, low access password for everyone)-- that's the only downside of this method. And if you're using %newwin% [[https://www.filemaker.com/12help/html/passwords.14.13.html | external authentication]], then it's no downside at all.

A linked calendar is also somewhat easier to update when SeedCode releases new versions-- though you still have to re-make any mods or customizations you've made.

to:
One downside to a linked file is that, like all multi-file solutions, you'll need to have your accounts and privilege sets in both files (unless you set the calendar file to auto-open with its own, low access password for everyone)-- that's the only downside of linking And if you're using %newwin% [[https://www.filemaker.com/12help/html/passwords.14.13.html | external authentication]], then it's no downside at all.
Changed line 11 from:
'''Embedding''' the calendar into your file means the calendar ends up as a layout (it's own layout, not part of an existing layout) in your file so you'll only have that one file when you're done. This is a more tedious integration process but if you follow our instructions carefully it doesn't take that long.
to:
'''Embedding''' the calendar into your file means the calendar ends up as a layout (it's own layout, not part of an existing layout) in your file so you'll discard our example file when you're done. This is a more tedious integration process but if you follow our instructions carefully it doesn't take that long.
May 20, 2014, at 08:04 PM by 65.102.176.83 -
Changed line 5 from:
'''Linking''' the two files is by far the easiest approach and if you often want to see the calendar in its own window then this is definitely the way to go. This is also the best option for folks who are newer to FileMaker.
to:
'''Linking''' the two files is '''by far''' the easiest approach and if you often want to see the calendar in its own window then this is definitely the way to go. This is also the best option for folks who are newer to FileMaker.
April 15, 2013, at 03:18 PM by 83.218.158.166 -
Changed lines 5-6 from:
'''Linking''' the two files is by far the easiest approach and if you often want to see the calendar in its own window then this is definitely the way to go. Like all mult-file solutions you'll need to have your accounts and privilege sets in both files (unless you set the calendar file to auto-open with its own low access password for everyone)-- that's the only downside of this method. And if you're using %newwin% [[https://www.filemaker.com/12help/html/passwords.14.13.html | external authentication]], then it's no downside at all.
to:
'''Linking''' the two files is by far the easiest approach and if you often want to see the calendar in its own window then this is definitely the way to go. This is also the best option for folks who are newer to FileMaker.

Like all multi-file solutions
you'll need to have your accounts and privilege sets in both files (unless you set the calendar file to auto-open with its own, low access password for everyone)-- that's the only downside of this method. And if you're using %newwin% [[https://www.filemaker.com/12help/html/passwords.14.13.html | external authentication]], then it's no downside at all.
April 15, 2013, at 03:13 PM by 83.218.158.166 -
April 15, 2013, at 03:08 PM by 83.218.158.166 -
Changed lines 1-206 from:
!! Integration Options.

Most folks will paste SeedCode Calendar into their file and use an events table they already have for the events they want to see in the calendar.

If you don't need to have the calendar "in" your file, you can still link the two files, pointing the calendar at your events table instead of the "SampleEvents" table it comes with. Linking in this way is much faster but means you'll have two files instead of one. (The chief disadvantage of this is that you have to have the same accounts and passwords in each file, unless you set the calendar file to auto-open with its own low access password for everyone.)

If this sounds like it might be for you, follow our instructions for the [[Quick Integration]].

The remainder of these instructions assume you already have a table whose records you want to see in the calendar. If you don't, you can just paste our "SampleEvents" table into your file and skip step 2 below.

You may also have more than one table (or more than one date field in a table) that you want to see in the calendar. Don't worry about that for now: get one table/field up and running and then you can come back and configure [[MultipleSources | additional event sources]].

!! Keys to Success

The most common mistake folks make integrating the calendar (or moving any FMP code from file to file) is performing steps in the order. FileMaker is very sensitive to the order in which new code is pasted into a file--create layouts before you paste in a script looking for that layout and all will be well; past the script in before the layout expected in that script has been created and you'll have some busted code that is particularly hard to unravel.

So, even if you're an experienced developer, follow the steps here carefully and in order--at least for your first calendar integration. =)

!! Step-by-Step Instructions: Pasting SeedCode Calendar into your File.

'''1. Backup your file.'''

-> Really.

-> And this is '''important''': review a [[YourFile | couple of things]] you may want to change in your file before you get started.

-> If you want to use the "SampleEvents" table in SeedCode Calendar as your events table, instead of a table you already have, just import it into your file in step 2 below and skip step 5.

'''2. Fields.'''

-> '''2.1''' Add two new fields to your events table from SeedCode Calendar's "SampleEvents" table:

--> zscTimestampStartCalcNum
--> zscTimestampEndCalcNum

-> Edit the definitions for these calcs, removing any leading / trailing comment tags if you pasted the fields in using FileMaker Advanced (that is, remove the /* and */ from the beginning and end of the calc). Then replace the DateStart, TimeStart, etc. fields referenced in these calculations with the relevant fields from your events table. Make sure both calcs return the form "number" and that both are indexed.

-> It may be that you don't have an end date field in your solution. You may also lack the time fields mentioned in the next steps (start and end times). The simplest thing is to add these fields to your events table: that makes the integration simpler and lets you take advantage of multi-day events should the scope of your events change. (Note that if you want to enforce that events never have times or never span more than 1 day you can use auto-enter calcs in these newly created fields to force them to be blank.)

-> If you create new fields, make sure the date fields are of the type "date" and the time fields are "time".

-> '''2.2''' Next, add the following Auto-Enter Calculated Value option to the TimeStart field in your events table (you can copy this here or from the definition in SampleEvents):

--> Case ( \\
Self = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ; \\
Self = Time ( 0 ; 0 ; 0 ) ; Time ( 0 ; 0 ; 1 ) ; \\
Self > Time ( 24 ; 0 ; 0 ) ; Self - Time ( 24 ; 0 ; 0 ) + 1 ; \\
Self )

-> Make sure you '''uncheck''' the "Do not replace existing value" checkbox. This Auto-Enter option is needed if you want events to be able to start at midnight.

-> '''2.3''' Now add the same Auto-Enter Calculated Value option to the TimeEnd field in your events table. Again, make sure you '''uncheck''' the "Do not replace existing value" checkbox. This Auto-Enter option is needed if you want events to be able to end at midnight.

-> '''2.4''' If you plan to use the calendar's gantt charts. repeating events, or email notifications add a few more fields from our SampleEvents to yours:

--> z_LinkedWithinProject
--> z_MilestoneSort
--> z_Notified
--> z_Repeating_id

'''3. Tables.'''

-> Import three tables into your file from SeedCode Calendar: CalendarInterface, CalendarRows, and CalendarColors. (If you're using data separation, add these tables to your interface file.)

-> If you're using FileMaker Advanced, you can just copy and paste the three tables. If you don't have Advanced, from your file select File / Import Records... / File and then select the SeedCodeCalendar file. Select the first of the three tables to import and for the target, select "New Table". FileMaker will create the new table and calcs for you but you'll have to come back and uncomment some of the calcs that couldn't find the items needed: come back after you've imported all three tables this way and remove the leading /* and trailing */ from your calcs.

-> If you don't have Advanced, and that sounds like too much, we'd be happy to complete this step for you, just send us your file.

%center%  https://www.seedcode.com/rootimages/stikipad/pro12/graph1.png

-> If you'd like to use the calendar's [[To-Do List]] and don't have your own To-Do table already, you can import our ToDoList table into your own file at this time as well. Leave it named "ToDoList" and that will keep things easier in the following steps.

->''You'll see we also have placeholder tables for contacts, projects, and phases. You presumably already have tables in your file representing these entities, and you'll line these up later. If you don't have a contacts or projects table, and wish you did, you may want to pause this integration and take a look at %newwin% [[https://www.seedcode.com/complete | SeedCode Complete]], which already has our calendar linked to a rich contacts and project management system.''

'''4. Value Lists.'''

-> Open SeedCode Calendar and recreate the seven value lists from our calendar in your file. Feel free to use your list of statuses and resources, but rename them to the value list names we're using in SeedCode Calendar: you can name them back later. The other values lists need to stay as they are, though you can feel free to change the time formats in "Calendar Times" to suit your tastes. You might want to do that later though, once you have this up and running.

-> Here, and in what follows, you don't need to import anything to do with SampleContacts or SampleProjects as you'll likely already have these things in your file. That is, you likely have a method of selecting contacts and projects and will want to use your existing method on the Event Details layout. (However, even if you do have an existing method, creating Contacts and Projects values lists now will let the Event Detail layout find those value lists when you paste the layout into you file. We also use this Projects value list on the calendar's filters: another good reason to create them now.)

'''5. Table Occurrences.'''

-> Select File / Manage / Database and navigate to the Relationships tab where you can see the "relationship graph" for your file. Click the little green plus button in the lower left to create a new occurrence of your events table (the table that has the records you want to see on the calendar) and name it "SampleEvents" (make sure there are no spaces in the table occurrence name). You can change this name later.

-> If you have a separate table of contacts you can create a new table occurrence of that as well and name it "SampleContacts" (again, with no quotes or spaces in the name). Link this to the SampleEvents table occurrence you just created using the same field matching you use elsewhere: this is likely from the SampleEvent's contact ID to the unique ID of the contact in SampleContacts. Do the same with projects, if you have projects, creating a new instance of Projects named "SampleProjects" and link it to SampleEvent's project ID. You can rename these table occurrences once you're up and running--just remember you'll need to edit one of the calendar's configuration scripts [[Renaming Tables | after you rename]].

'''6. Relationships'''

-> '''6.1 Relationships Part 1.''' Staying on the Relationships tab, link "CalendarRows" to "CalendarInterface" to "CalendarColors" as shown below. Double check that the table occurrence names match what we have in the sample file, and make sure the open end of the &#8805; operator is pointing toward "CalendarInterface":

%center%  https://www.seedcode.com/rootimages/stikipad/pro12/graph2.png

-> At this point, if you want to show event colors in list view as we do in the Event List or Event Detail layouts, copy our field "z_sc_ColorCalc" from SampleEvents and add it to your events table. Remove the /* and */ from the beginning and end of the calc and replace our use of the field "status" with the equivalent field in your events table: this is the field we used to color code events in the calendar.

-> '''6.5. Relationships Part 2.''' ''If you intend to remove the Gantt chart you can skip this section.''

-> If you'll be using the Gantt Chart you'll want to connect a few more things in the graph. First, create a relationship from CalendarRows to SampleEvents like this, where "id" is the primary key (the unique ID) in your events table. :

%center width="500%  https://www.seedcode.com/rootimages/stikipad/pro12/graph3.png

-> Then attach SampleEvents to your Contacts, Projects, and possibly your Phases table occurrences, as shown here:

%center% https://www.seedcode.com/rootimages/stikipad/pro12/graph4.png

-> It probably make sense to create new instances of these to attach to SampleEvents, but you don't have to. You'll likely want to rename your table occurrences to "Sample..." for now so that items pasted in later will line up. (Big time saver) If you don't have a Phases table, don't worry: phases are completely optional.

'''7. Layouts Part 1.'''

-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required, except for "Demo Expired"). This is most easily done by creating the first layout listed below, deleting the header and footer part, and duplicating it to create the others.

-> ''Note: it is important that you don't already have any layouts (or layout folders) with the same name as any of the layouts below. If you do, please rename your layouts or folders before continuing. (And yes, FMP's design functions can't tell the difference between a layout and a folder, so a folder named "Calendar" will cause problems also.)''

-> Here is how to create that first layout: Create the layout and then visit Layout Setup and uncheck the box beside "Show field frames when record is active". Base the layout on the Classic theme. Also uncheck the box to enable QuickFind. (If you want to search the calendar using QuickFind you can leave this enabled on the EventList layout, or use %newwin% [[https://www.seedcode.com/cp-app/ste_cat/fmsearchresults | fmSearchResults]] to extend QuickFind. Do this after you've followed these instructions and are up and running.) Keep duplicating and renaming layouts making sure to switch "Show records from" to match the associated table shown in the list below.

-> Again, you don't need to add the sample contact, project, and phase layouts unless you don't have any of your own. But you '''do''' need to create the layouts in the Developer and Additional Skins folders.

-> You may want to create the separator layouts we have as well (these are based on CalendarInterface) but that is just cosmetic. Make sure each layout is based on the table occurrence shown below.

-> Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and that the headers and footers are deleted from each.

-> Finally, delete the default layouts created when you imported tables in step 3.

-> Now you may already have layouts you want to use for your Event List and Event Details. If so, take a moment to read about that here: using [[your own Event layouts]].

-> If you're using the [[To-Do List]] add the To-Do Details and To-Do List layouts as well.

%center% https://www.seedcode.com/rootimages/stikipad/pro12/layoutlist.png

'''8. Scripts.'''

-> Import the scripts from SeedCode Calendar. When importing, just click the check box beside the folder "SeedCode Calendar" and all the scripts within that folder will import. There will be a number of errors reports when you import: this is normal. In "Setup" below we'll remap some of the fields and settings in these scripts to values in your file.

-> However, if any scripts are reported as being "renamed" because of a conflict, quickly scan the imported scripts for names ending "2" and correct them. For example, the calendar has a script called "Upon Opening". If you already have one with that name ours will get imported as "Upon Opening 2". To fix this '''rename yours''' to something like "Upon Opening Main" and then rename ours to "Upon Opening". Our scripts must have the same names as they do in the SeedCode Calendar file for the following step to work.

'''9. Layouts Part 2.'''

-> Now copy the layout contents from each layout in SeedCode Calendar and paste them into the layout of the same name in your file. Do every layout, including Calendar Rows and Calendar Color Records. You'll be warned that you'll be increasing the height of each layout; that's OK.

-> While the layout heights in FileMaker 12 take care of themselves automatically, the layout widths do not. You'll need to manually move the right edge of the layout out to the same place it is on the layouts in our file (for most layouts this is flush with the rightmost object edge).

%center%  https://www.seedcode.com/rootimages/stikipad/pro12/layoutwidth.png

-> When you get to Event Details feel free to edit this layout as you see fit, adding your own fields and buttons. Just be sure to keep the following 3 objects: the "repeat" button, the "show repts..." button below it, and the large "close..." button at the bottom of the screen. You can come back and edit this layout later, for now, just get the Summary, Date, and Time fields lined up with the relevant fields in your events table.

-> Just as you needed to click on fields on Event Details and point them at the proper fields in your table, you'll need to do the same to the Event List layout, and the on the To-Do Details and To-Do list, if you're using those, Again, you can map the basic date, time, and summary fields now so you know the calendar is working. We have a note at the end of these instructions reminding you to come back here and finish cleaning these layouts up.

'''10. Layout Script Triggers.'''

-> Assign script triggers. Since layout level script triggers don't come over when you copy and paste layout elements, you'll have to recreate these. Fortunately there are only a few.

--> Layout: Calendar Home & Docs (1 trigger)
--> Trigger: OnRecordLoad (in Browse Mode)
--> Script: "Load Home Layout"

--> Layout: Calendar (1 trigger)
--> Trigger: OnRecordLoad (in Browse and Find Mode)
--> Script: "Load Calendar Layout"
--> (Do this on "Calendar - no Side Menu" also, along with the "Calendar iPad" and "Calendar iPad - no Side Menu" layouts.)

--> Layout: Event Details (1 trigger)
--> Trigger: OnRecordLoad (in Browse Mode)
--> Script: "On Event Record Load"

--> Layout: To-Do Details (1 trigger)
--> Trigger: OnRecordLoad (in Browse Mode)
--> Script: "On Event Record Load"

--> Layout: Repeat Options (1 trigger)
--> Trigger: OnRecordLoad (in Browse Mode)
--> Script: "Set initial repeat variables"

--> Return to the Calendar Home layout when you're done and enter Browse Mode.

'''11. Setup.'''

-> Here is where you start making the calendar your own, editing the scripts that control the calendars behavior and default settings. Read through these scripts slowly: you won't need to change every setting in them, but you'll change many and it's good to take your time so you remember what settings are available to you.

-> '''11.1 Configure the calendar.''' Edit the scripts "Load Calendar Settings - On Startup..." and "Load Source Settings at Startup --- Describe Your Sources Here ---" and follow the comments throughout the script, changing settings and field mappings as necessary.

-> '''11.2 Map your data.''' Go to the layout "Source No 1" (in the Developer layout folder) and follow the directions on the layout to map the fields there to the fields in your SampleEvents table. Map the "Summary" to a simple field for now like your event's title, just to get you up and running, then return here and try mapping the summary to something more interesting to create a [[MultiLineEvents | multi-line event]] display.

-> A couple tips on field mapping:

--> Events with just a single date should have a start date: if your event has just an end date the calendar will fail. The same goes for times: if there is only one time, make it the start time.

--> Don't use calcs for things like the dates, times, or resources. The calendar wants to edit these values when you drag items around, and it can't edit calcs. Use auto-enter calculations instead if you must.

'''12. Clean Up.'''

-> Rename your Sample Events table occurrence to something that makes more sense for you. And add the script "Upon Opening" to your file's opening script, removing the go to layout stuff if you'd like. If you're using multiple windows or renaming windows in your own upon opening script, you may want to run our Upon Opening routine the first time your users open the calendar in a new window rather than at the beginning. 

'''13. Run a Script.'''

-> That's it. Run the script "Upon Opening" script and you should see your events in the day view.

Enjoy!

!! Next Steps

Now that you've gotten up and running, you'll likely want to return to a few places and do a more thorough job of mapping the calendar to your events. Here are the places we like to revisit:

-> Event Details. You may have left some fields unmapped here. You'll probably also want to double check the arrows / buttons which jump from an event to its related contact or project. Learn more about these here: [[jump to my contact]].

-> Event List. You may have unmapped fields here as well. Also be sure to enter layout mode and double check the summary parts on the [[Event List]].

-> To-Do Details and List. If you're using the To-Do list, you likely skipped mapping some fields on its detail and list layouts as well.
to:
!! Two Options: Linking and Embedding

There are two ways to get the calendar to work with your file. You can '''link''' the SeedCode Calendar file to your, or you can '''embed''' it, pasting the fields, scripts, and layouts required from our file into yours.

'''Linking''' the two files is by far the easiest approach and if you often want to see the calendar in its own window then this is definitely the way to go. Like all mult-file solutions you'll need to have your accounts and privilege sets in both files (unless you set the calendar file to auto-open with its own low access password for everyone)-- that's the only downside of this method. And if you're using %newwin% [[https://www.filemaker.com/12help/html/passwords.14.13.html | external authentication]], then it's no downside at all.

A linked calendar is also somewhat easier to update when SeedCode releases new versions-- though you still have to re-make any mods or customizations you've made.

-> Learn how to [[Quick Integration | Link the Calendar]].

'''Embedding''' the calendar into your file means the calendar ends up as a layout (it's own layout, not part of an existing layout) in your file so you'll only have that one file when you're done. This is a more tedious integration process but if you follow our instructions carefully it doesn't take that long.

-> Learn how to [[Embedding The Calendar | Embed the Calendar]].
January 07, 2013, at 12:56 AM by 98.245.113.231 -
Changed lines 65-66 from:
-> If you're using FileMaker Advanced, you can just copy and paste the three tables. If you don't have Advanced, from your file select File / Import Records... / File and then select the SeedCodeCalendar file. Select the first of the three tables to import and for the target, select "New Table". FileMaker will create the new table and calcs for you but you'll have to come back and uncomment some of the calcs that couldn't find the items needed: come back after you've imported all three tables this way and remove the leading /* and trailing */ form your calcs.
to:
-> If you're using FileMaker Advanced, you can just copy and paste the three tables. If you don't have Advanced, from your file select File / Import Records... / File and then select the SeedCodeCalendar file. Select the first of the three tables to import and for the target, select "New Table". FileMaker will create the new table and calcs for you but you'll have to come back and uncomment some of the calcs that couldn't find the items needed: come back after you've imported all three tables this way and remove the leading /* and trailing */ from your calcs.
January 07, 2013, at 12:49 AM by 98.245.113.231 -
Changed lines 31-32 from:
-> '''2.1''' Add two new fields to your event's table from SeedCode Calendar's "SampleEvents" table:
to:
-> '''2.1''' Add two new fields to your events table from SeedCode Calendar's "SampleEvents" table:
January 03, 2013, at 10:35 PM by 206.124.30.34 -
Changed lines 5-6 from:
If you don't need to have the calendar "in" your file, you can still link the two files, pointing the calendar at your events table instead of the SampleEvents table it comes with. Linking in this way is much faster but means you'll have two files instead of one. (The chief disadvantage of this is that you have to have the same accounts and passwords in each file, unless you set the calendar file to auto-open with its own low access password for everyone.)
to:
If you don't need to have the calendar "in" your file, you can still link the two files, pointing the calendar at your events table instead of the "SampleEvents" table it comes with. Linking in this way is much faster but means you'll have two files instead of one. (The chief disadvantage of this is that you have to have the same accounts and passwords in each file, unless you set the calendar file to auto-open with its own low access password for everyone.)
Changed lines 9-10 from:
The remainder of these instructions assume you already have a table whose records you want to see in the calendar. If you don't, you can just paste our SampleEvents table into your file and skip step 2 below.
to:
The remainder of these instructions assume you already have a table whose records you want to see in the calendar. If you don't, you can just paste our "SampleEvents" table into your file and skip step 2 below.
Changed lines 27-28 from:
-> If you want to use the Sample Events table in SeedCode Calendar as your events table, instead of a table you already have, just import it into your file in step 2 below and skip step 5.
to:
-> If you want to use the "SampleEvents" table in SeedCode Calendar as your events table, instead of a table you already have, just import it into your file in step 2 below and skip step 5.
Changed lines 31-32 from:
-> '''2.1''' Add two new fields to your event's table from SeedCode Calendar's Sample Events table:
to:
-> '''2.1''' Add two new fields to your event's table from SeedCode Calendar's "SampleEvents" table:
Changed lines 36-37 from:
-> Edit the definitions for these calcs, removing any leading / trailing comment tags if you pasted the fields in using FileMaker Advanced (that is, remove the /* and */ from the beginning and end of the calc). Then replace the DateStart, TimeStart, etc. fields refrenced in these calculations with the relevant fields from your events table. Make sure both calcs return the form "number" and that both are indexed.
to:
-> Edit the definitions for these calcs, removing any leading / trailing comment tags if you pasted the fields in using FileMaker Advanced (that is, remove the /* and */ from the beginning and end of the calc). Then replace the DateStart, TimeStart, etc. fields referenced in these calculations with the relevant fields from your events table. Make sure both calcs return the form "number" and that both are indexed.
Changed lines 63-64 from:
-> Import three tables into your file from SeedCode Calendar: CalendarInterface, CalendarRows,  and CalendarColors. (If you're using data separation, add these tables to your interface file.)
to:
-> Import three tables into your file from SeedCode Calendar: CalendarInterface, CalendarRows, and CalendarColors. (If you're using data separation, add these tables to your interface file.)
Changed lines 77-78 from:
-> Open SeedCode Calendar and recreate the 7 value lists from our calendar in your file. Feel free to use your list of statuses and resources, but rename them to the value list names we're using in SeedCode Calendar: you can name them back later. The other values lists need to stay as they are, though you can feel free to change the time formats in "Calendar Times" to suit your tastes. You might want to do that later though, once you have this up and running.
to:
-> Open SeedCode Calendar and recreate the seven value lists from our calendar in your file. Feel free to use your list of statuses and resources, but rename them to the value list names we're using in SeedCode Calendar: you can name them back later. The other values lists need to stay as they are, though you can feel free to change the time formats in "Calendar Times" to suit your tastes. You might want to do that later though, once you have this up and running.
Changed lines 95-96 from:
-> '''6.5. Relationships Part 2.''' ''If you intend to remove the gantt chart you can skip this section.''
to:
-> '''6.5. Relationships Part 2.''' ''If you intend to remove the Gantt chart you can skip this section.''
November 18, 2012, at 04:16 PM by 50.132.84.245 -
Changed lines 85-86 from:
-> If you have a separate table of contacts you can create a new table occurrence of that as well and name it "SampleContacts" (again, with no quotes or spaces in the name). Link this to the SampleEvents table occurrence you just created using the same field matching you use elsewhere: this is likely from the SampleEvent's contact ID to the unique ID of the contact in SampleContacts. Do the same with projects, if you have projects, creating a new instance of Projects named "SampleProjects" and link it to SampleEvent's project ID. You can rename these table occurrences once you're up and running.
to:
-> If you have a separate table of contacts you can create a new table occurrence of that as well and name it "SampleContacts" (again, with no quotes or spaces in the name). Link this to the SampleEvents table occurrence you just created using the same field matching you use elsewhere: this is likely from the SampleEvent's contact ID to the unique ID of the contact in SampleContacts. Do the same with projects, if you have projects, creating a new instance of Projects named "SampleProjects" and link it to SampleEvent's project ID. You can rename these table occurrences once you're up and running--just remember you'll need to edit one of the calendar's configuration scripts [[Renaming Tables | after you rename]].
October 22, 2012, at 04:02 PM by 107.2.189.216 -
Changed lines 178-179 from:
-> '''11.1 Configure the calendar.''' Edit the script "Load Calendar Settings - On Startup..." and follow the comments throughout the script, changing settings and field mappings as necessary.
to:
-> '''11.1 Configure the calendar.''' Edit the scripts "Load Calendar Settings - On Startup..." and "Load Source Settings at Startup --- Describe Your Sources Here ---" and follow the comments throughout the script, changing settings and field mappings as necessary.
August 12, 2012, at 05:32 PM by 50.132.84.245 -
Changed lines 77-78 from:
-> Open SeedCode Calendar and recreate the 7 value lists from our calendar in your file. Feel free to use your list of statuses and resources, but rename them to the names we're using in SeedCode Calendar: you can name them back later. The other values lists need to stay as they are, though you can feel free to change the time formats in "Calendar Times" to suit your tastes. You might want to do that later though, once you have this up and running.
to:
-> Open SeedCode Calendar and recreate the 7 value lists from our calendar in your file. Feel free to use your list of statuses and resources, but rename them to the value list names we're using in SeedCode Calendar: you can name them back later. The other values lists need to stay as they are, though you can feel free to change the time formats in "Calendar Times" to suit your tastes. You might want to do that later though, once you have this up and running.
August 09, 2012, at 02:18 AM by 50.132.84.245 -
Changed lines 109-110 from:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required). This is most easily done by creating the first layout listed below, deleting the header and footer part, and duplicating it to create the others.
to:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required, except for "Demo Expired"). This is most easily done by creating the first layout listed below, deleting the header and footer part, and duplicating it to create the others.
August 07, 2012, at 05:14 PM by 71.212.48.84 -
Added lines 111-112:
-> ''Note: it is important that you don't already have any layouts (or layout folders) with the same name as any of the layouts below. If you do, please rename your layouts or folders before continuing. (And yes, FMP's design functions can't tell the difference between a layout and a folder, so a folder named "Calendar" will cause problems also.)''
August 07, 2012, at 05:11 PM by 71.212.48.84 -
Changed lines 152-153 from:
--> (Do this on each of the four calendar layouts.)
to:
August 07, 2012, at 05:10 PM by 71.212.48.84 -
Added lines 40-41:
-> If you create new fields, make sure the date fields are of the type "date" and the time fields are "time".
August 07, 2012, at 05:09 PM by 71.212.48.84 -
Added lines 38-39:
-> It may be that you don't have an end date field in your solution. You may also lack the time fields mentioned in the next steps (start and end times). The simplest thing is to add these fields to your events table: that makes the integration simpler and lets you take advantage of multi-day events should the scope of your events change. (Note that if you want to enforce that events never have times or never span more than 1 day you can use auto-enter calcs in these newly created fields to force them to be blank.)
August 07, 2012, at 02:50 PM by 50.132.84.245 -
Changed lines 48-57 from:
-> '''2.3''' Now add the following Auto-Enter Calculated Value option to the TimeEnd field in your events table:

--> Case ( //
Self = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ; //
Self = Time ( 0 ; 0 ; 0 ) ; Time ( 0 ; 0 ; 1 ) ; //
Self > Time ( 24 ; 0 ; 0 ) ; Self - Time ( 24 ; 0 ; 0 ) + 1 ; //
Self )

->
Again, make sure you '''uncheck''' the "Do not replace existing value" checkbox. This Auto-Enter option is needed if you want events to be able to end at midnight.
to:
-> '''2.3''' Now add the same Auto-Enter Calculated Value option to the TimeEnd field in your events table. Again, make sure you '''uncheck''' the "Do not replace existing value" checkbox. This Auto-Enter option is needed if you want events to be able to end at midnight.
August 06, 2012, at 03:21 AM by 50.132.84.245 -
Changed lines 58-59 from:
-> '''2.4''' If you plan to use the calendar's gantt charts or email notifications add a few more fields from our SampleEvents to yours:
to:
-> '''2.4''' If you plan to use the calendar's gantt charts. repeating events, or email notifications add a few more fields from our SampleEvents to yours:
Changed lines 63-64 from:
to:
--> z_Repeating_id
August 06, 2012, at 02:25 AM by 50.132.84.245 -
August 06, 2012, at 02:16 AM by 50.132.84.245 -
Changed lines 9-10 from:
The remainder of these instructions assume you already have a table whose records you want to see in the calendar. If you don't, you can just paste our SampleEvents table into your file and skip to step 2 below.
to:
The remainder of these instructions assume you already have a table whose records you want to see in the calendar. If you don't, you can just paste our SampleEvents table into your file and skip step 2 below.
August 06, 2012, at 02:16 AM by 50.132.84.245 -
Changed lines 13-14 from:
!! Tips
to:
!! Keys to Success
August 06, 2012, at 02:15 AM by 50.132.84.245 -
Added lines 9-18:
The remainder of these instructions assume you already have a table whose records you want to see in the calendar. If you don't, you can just paste our SampleEvents table into your file and skip to step 2 below.

You may also have more than one table (or more than one date field in a table) that you want to see in the calendar. Don't worry about that for now: get one table/field up and running and then you can come back and configure [[MultipleSources | additional event sources]].

!! Tips

The most common mistake folks make integrating the calendar (or moving any FMP code from file to file) is performing steps in the order. FileMaker is very sensitive to the order in which new code is pasted into a file--create layouts before you paste in a script looking for that layout and all will be well; past the script in before the layout expected in that script has been created and you'll have some busted code that is particularly hard to unravel.

So, even if you're an experienced developer, follow the steps here carefully and in order--at least for your first calendar integration. =)

August 06, 2012, at 02:05 AM by 50.132.84.245 -
Changed lines 136-139 from:
-> Just as you needed to click on fields on Event Details and point them at the proper fields in your table, you'll need to do the same to the Event List layout.

-> You'll also need to repoint some fields on the Gantt Chart tab of the Calendar layouts. If you're not using the gantt charts, skip on to step 10. Otherwise pause here to [[Edit Fields on the Gantt Chart]] or make a note to come back here after you're up
and running.
to:
-> Just as you needed to click on fields on Event Details and point them at the proper fields in your table, you'll need to do the same to the Event List layout, and the on the To-Do Details and To-Do list, if you're using those, Again, you can map the basic date, time, and summary fields now so you know the calendar is working. We have a note at the end of these instructions reminding you to come back here and finish cleaning these layouts up.
August 06, 2012, at 01:19 AM by 50.132.84.245 -
Changed lines 198-200 from:
-> Event List. You may have unmapped fields here as well. Also be sure to enter layout mode and double check the summary parts on the [[Event List]].
to:
-> Event List. You may have unmapped fields here as well. Also be sure to enter layout mode and double check the summary parts on the [[Event List]].

-> To-Do Details and List. If you're using the To-Do list, you likely skipped mapping some fields on its detail and list layouts as well
.
August 06, 2012, at 01:16 AM by 50.132.84.245 -
Changed lines 190-198 from:
Enjoy!
to:
Enjoy!

!! Next Steps

Now that you've gotten up and running, you'll likely want to return to a few places and do a more thorough job of mapping the calendar to your events. Here are the places we like to revisit:

-> Event Details. You may have left some fields unmapped here. You'll probably also want to double check the arrows / buttons which jump from an event to its related contact or project. Learn more about these here: [[jump to my contact]].

-> Event List. You may have unmapped fields here as well. Also be sure to enter layout mode and double check the summary parts on the [[Event List]].
August 06, 2012, at 01:08 AM by 50.132.84.245 -
Changed lines 172-179 from:
-> '''11.1 Configure the calendar.''' Edit the script "Load Calendar Settings - On Startup..." and follow the comments changing values as necessary.

-> Edit the script "Create Edit Delete Event
..." and you'll see a few fields "missing". Point these at the fields in your events table with the same name. You can tell which field to use from the names of the variable we're setting into them.

-> '''11.3 Map your data.''' Then go to the layout "Source No 1" and follow the directions on the layout to map the fields there
to the fields in your SampleEvents table. Map the "Summary" to a simple field for now like your event's title, just to get you up and running, then return here and try mapping the summary to something more interesting to create a [[MultiLineEvents | multi-line event]] display.

-> A couple tips
:
to:
-> '''11.1 Configure the calendar.''' Edit the script "Load Calendar Settings - On Startup..." and follow the comments throughout the script, changing settings and field mappings as necessary.

-> '''11
.2 Map your data.''' Go to the layout "Source No 1" (in the Developer layout folder) and follow the directions on the layout to map the fields there to the fields in your SampleEvents table. Map the "Summary" to a simple field for now like your event's title, just to get you up and running, then return here and try mapping the summary to something more interesting to create a [[MultiLineEvents | multi-line event]] display.

-> A couple tips on field
mapping:
Changed lines 180-181 from:
--> Don't use calcs for things like the dates, times, or resources. The calendar wants to edit these values when you drag items around, and it can't edit calcs. Use auto-enter calculations instead if you must. 
to:
--> Don't use calcs for things like the dates, times, or resources. The calendar wants to edit these values when you drag items around, and it can't edit calcs. Use auto-enter calculations instead if you must.
August 06, 2012, at 01:05 AM by 50.132.84.245 -
Deleted lines 173-176:
-> '''11.2 Sort your records.''' Edit the script "Sort FileMaker Records..." and follow the instructions to sort your records by date / time ascending, editing the sort step there to use fields from your events table.

-> If you're using the gantt chart, edit the script "Sort FileMaker Records for Gantt Chart..." following the instructions in the script's comments.

August 06, 2012, at 01:04 AM by 50.132.84.245 -
Added lines 170-171:
-> Here is where you start making the calendar your own, editing the scripts that control the calendars behavior and default settings. Read through these scripts slowly: you won't need to change every setting in them, but you'll change many and it's good to take your time so you remember what settings are available to you.
August 06, 2012, at 01:01 AM by 50.132.84.245 -
Added lines 144-148:
--> Layout: Calendar Home & Docs (1 trigger)
--> Trigger: OnRecordLoad (in Browse Mode)
--> Script: "Load Home Layout"
--> (Do this on each of the four calendar layouts.)

Changed lines 152-153 from:
--> (Do this on each of the four calendar layouts.)
to:
--> (Do this on "Calendar - no Side Menu" also, along with the "Calendar iPad" and "Calendar iPad - no Side Menu" layouts.)
Added lines 158-165:
--> Layout: To-Do Details (1 trigger)
--> Trigger: OnRecordLoad (in Browse Mode)
--> Script: "On Event Record Load"

--> Layout: Repeat Options (1 trigger)
--> Trigger: OnRecordLoad (in Browse Mode)
--> Script: "Set initial repeat variables"

August 06, 2012, at 12:37 AM by 50.132.84.245 -
Changed lines 106-107 from:
-> Again, you don't need to add the contact and projects layouts unless you don't have any of your own. But you '''do''' need to create the layouts in the Developer and Additional Skins folders.
to:
-> Again, you don't need to add the sample contact, project, and phase layouts unless you don't have any of your own. But you '''do''' need to create the layouts in the Developer and Additional Skins folders.
August 06, 2012, at 12:35 AM by 50.132.84.245 -
Changed lines 136-143 from:
-> Just as you needed to click on fields on Event Details and point them at the proper fields in your table, you'll need to do the same to the Event List layout and to the Gantt Chart tab of the Calendar layouts. ''If you're not using the gantt charts, skip on to step 10.''

-> On the gantt tab you only need to edit the three fields to the left of the vertical black line. These fields are stacked on top of each other, so click on the top one, dragging it down and out of the way: hold the shift key down while dragging to you don't move the field to the left or right. Do this again with the next field until your layout looks like this:

%center% https://www.seedcode.com/rootimages/stikipad/nextcal/ganttfields.png

-> It doesn't matter in which order you drag the fields, but you'll point them at their correct fields in your table starting with the one that is furthest to the left (that is the lowest one in the illustration above). Point that field at the name of your Project in SampleProjects. Point the next field in from the left at your Phase's name from SamplePhases if you have phases: if you don't have phases, delete the field. Finally point the one starting furthest to the right at the Summary field in your Sample Events table. Then move the two fields back up to their original positions
.
to:
-> Just as you needed to click on fields on Event Details and point them at the proper fields in your table, you'll need to do the same to the Event List layout.

-> You'll also need to repoint some fields on
the Gantt Chart tab of the Calendar layouts. If you're not using the gantt charts, skip on to step 10. Otherwise pause here to [[Edit Fields on the Gantt Chart]] or make a note to come back here after you're up and running.
August 06, 2012, at 12:31 AM by 50.132.84.245 -
Deleted lines 137-138:
-> Navigating to the gantt tab means moving one of our button bars: you'll find notes about how to get to this here: %newwin% [[CalendarTabs | working with the calendar tabs]].
August 06, 2012, at 12:29 AM by 50.132.84.245 -
Changed lines 130-131 from:
-> While the layout heights in FileMaker 12 take care of themselves automatically, the layout widths do not.
to:
-> While the layout heights in FileMaker 12 take care of themselves automatically, the layout widths do not. You'll need to manually move the right edge of the layout out to the same place it is on the layouts in our file (for most layouts this is flush with the rightmost object edge).

%center%  https://www.seedcode.com/rootimages/stikipad/pro12/layoutwidth.png

August 06, 2012, at 12:22 AM by 50.132.84.245 -
Deleted lines 125-128:
 > > H E R E

-> If you're using the gantt chart, edit the script "Record Gantt Chart Field Names..." and follow the instructions in each SetVariable line to point the script at the Project and Phase fields in your tables. Some lines may already be correct if you've named your fields the same way we have. You may need to create a couple of fields in your Project's table, and create the field "z_LinkedWithinProject" in SampleEvents if you haven't already. While Phases aren't required-- you can skip the phase fields if you're not using phases, all 3 project fields and the one field from SampleEvents mentioned in this script are required.

Changed lines 128-129 from:
-> Now copy the layout contents from each layout in SeedCode Calendar and paste them into the layout of the same name in your file. Do every layout, including Calendar Rows and Calendar Color Records. You'll be warned that you'll be increasing the size of each layout; that's OK.
to:
-> Now copy the layout contents from each layout in SeedCode Calendar and paste them into the layout of the same name in your file. Do every layout, including Calendar Rows and Calendar Color Records. You'll be warned that you'll be increasing the height of each layout; that's OK.

-> While the layout heights in FileMaker 12 take care of themselves automatically, the layout widths do not
.
August 05, 2012, at 10:39 PM by 50.132.84.245 -
Added lines 126-127:
 > > H E R E
August 05, 2012, at 10:37 PM by 50.132.84.245 -
Deleted lines 113-114:
%center% https://www.seedcode.com/rootimages/stikipad/nextcal/layoutlist.png
Added lines 118-119:
%center% https://www.seedcode.com/rootimages/stikipad/pro12/layoutlist.png
August 05, 2012, at 10:32 PM by 50.132.84.245 -
August 05, 2012, at 10:32 PM by 50.132.84.245 -
Changed lines 106-107 from:
-> Again, you don't need to add the contact and projects layouts unless you don't have any of your own.
to:
-> Again, you don't need to add the contact and projects layouts unless you don't have any of your own. But you '''do''' need to create the layouts in the Developer and Additional Skins folders.
August 05, 2012, at 10:31 PM by 50.132.84.245 -
Changed lines 98-99 from:
-> It probably make sense to create new instances of these to attach to SampleEvents, but you don't have to. You'll likely want to rename your table occurrences to "Sample..." for now so that items pasted in later will line up. (Big time saver) If you don't have a Phases table, don't worry; phases are completely optional.
to:
-> It probably make sense to create new instances of these to attach to SampleEvents, but you don't have to. You'll likely want to rename your table occurrences to "Sample..." for now so that items pasted in later will line up. (Big time saver) If you don't have a Phases table, don't worry: phases are completely optional.
Changed lines 102-105 from:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required). This is most easily done by creating the first layout listed below, deleting the header and footer part, and duplicating it to create the others. Create the layout and then visit Layout Setup and uncheck the box beside "Show field frames when record is active". Also uncheck the box to enable QuickFind if you're using FileMaker 11. (If you want to search the calendar using QuickFind you can leave this enabled on the EventList layout, or use %newwin% [[https://www.seedcode.com/cp-app/ste_cat/fmsearchresults | fmSearchResults]] to extend QuickFind. Do this after you've followed these instructions and are up and running.) Keep duplicating and renaming layouts making sure to switch "Show records from" to match the associated table shown in the list below.

-> Again, you don't need to add the contact layouts unless you don't have any of your own.
to:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required). This is most easily done by creating the first layout listed below, deleting the header and footer part, and duplicating it to create the others.

-> Here is how to create that first layout: Create
the layout and then visit Layout Setup and uncheck the box beside "Show field frames when record is active". Base the layout on the Classic theme. Also uncheck the box to enable QuickFind. (If you want to search the calendar using QuickFind you can leave this enabled on the EventList layout, or use %newwin% [[https://www.seedcode.com/cp-app/ste_cat/fmsearchresults | fmSearchResults]] to extend QuickFind. Do this after you've followed these instructions and are up and running.) Keep duplicating and renaming layouts making sure to switch "Show records from" to match the associated table shown in the list below.

-> Again, you don't need to add the contact and projects layouts unless you don't have any of your own.
August 05, 2012, at 10:28 PM by 50.132.84.245 -
Added lines 48-53:
-> '''2.4''' If you plan to use the calendar's gantt charts or email notifications add a few more fields from our SampleEvents to yours:

--> z_LinkedWithinProject
--> z_MilestoneSort
--> z_Notified

Deleted lines 99-110:
-> Once your section of the graph looks like ours above, you can create a couple new fields in your Projects table, and in your Phases table if you're using Phases.

--> In Projects create the calc "ProjectDateEarliestEventCalc" returning the type Date equal to: Min ( SampleEvents::DateStart )

--> Also in Projects create the calc "ProjectDateLatestEventCalc" returning the type Date equal to: Max ( Max ( SampleEvents::DateEnd ) ; Max ( SampleEvents::DateStart ) )

--> In Phases (if you're using Phases) create the calc "PhaseDateEarliestEventCalc" returning the type Date equal to: Min ( SampleEvents::DateStart )

--> Also in Phases create the calc "PhaseDateLatestEventCalc" returning the type Date equal to: Max ( Max ( SampleEvents::DateEnd ) ; Max ( SampleEvents::DateStart ) )

--> Finally, in SampleEvents, create a new number field called "z_LinkedWithinProject"

August 05, 2012, at 10:25 PM by 50.132.84.245 -
Changed lines 90-93 from:
%center% https://www.seedcode.com/rootimages/stikipad/nextcal/ganttgraph.png

-> It probably make sense to create new instances of these to attach to SampleEvents, but you don't have to. You may, however, want to rename your table occurrences to "Sample..." for now so that items pasted in later will line up. If you don't have a Phases table, don't worry; phases are completely optional.
to:
%center% https://www.seedcode.com/rootimages/stikipad/pro12/graph4.png

-> It probably make sense to create new instances of these to attach to SampleEvents, but you don't have to. You'll likely want to rename your table occurrences to "Sample..." for now so that items pasted in later will line up. (Big time saver) If you don't have a Phases table, don't worry; phases are completely optional.
August 05, 2012, at 10:21 PM by 50.132.84.245 -
Changed lines 84-85 from:
-> If you'll be using the Gantt Chart you'll want to connect a few more things in the graph. First, create a relationship from CalendarRows to SampleEvents like this:
to:
-> If you'll be using the Gantt Chart you'll want to connect a few more things in the graph. First, create a relationship from CalendarRows to SampleEvents like this, where "id" is the primary key (the unique ID) in your events table. :
Changed lines 88-90 from:

-> Where _id is the primary key (the unique ID) in your events table. Then attach SampleEvents to your Contacts, Projects, and possibly your Phases table occurrences, as shown here:
to:
-> Then attach SampleEvents to your Contacts, Projects, and possibly your Phases table occurrences, as shown here:
August 05, 2012, at 10:19 PM by 50.132.84.245 -
Changed lines 86-87 from:
--> CalendarEventUIDCalc_FirstValue = _id
to:
%center width="500%  https://www.seedcode.com/rootimages/stikipad/pro12/graph3.png

August 05, 2012, at 10:18 PM by 50.132.84.245 -
August 05, 2012, at 10:17 PM by 50.132.84.245 -
Changed lines 76-85 from:
-> '''6.1 Relationships Part 1.''' Staying on the Relationships tab, link "CalendarRows" to "CalendarInterface" to "CalendarColors" as shown below. Double check that the table occurrence names match what we have in the sample file.

%center% https://www.seedcode.com/rootimages/stikipad/pro12/graph1.png

-> At this point, if you want to show event colors in list view as we do in the Event List or Event Detail layouts, copy our field "z_ColorCalc" from Sample Events and add it to your events table. Remove the /* and */
from the beginning and end of the calc and replace our use of the field "status" with the equivalent field in your events table: this is the field we used to color code events in the calendar.

-> '''6.5. Relationships Part 2.''' ''The [[gantt chart]] was introduced in version 5.6 of
the calendar. If you're not using the gantt chart you can skip this section.''

-> If you'll be using the Gantt Charts you'll want to connect a few more things in the graph. First, create a relationship from CalendarRows to SampleEvents like this:
to:
-> '''6.1 Relationships Part 1.''' Staying on the Relationships tab, link "CalendarRows" to "CalendarInterface" to "CalendarColors" as shown below. Double check that the table occurrence names match what we have in the sample file, and make sure the open end of the &#8805; operator is pointing toward "CalendarInterface":

%center%  https://www.seedcode.com/rootimages/stikipad/pro12/graph2.png

-> At this point, if you want to show event colors in list view as we do in the Event List or Event Detail layouts, copy our field "z_sc_ColorCalc"
from SampleEvents and add it to your events table. Remove the /* and */ from the beginning and end of the calc and replace our use of the field "status" with the equivalent field in your events table: this is the field we used to color code events in the calendar.

->
'''6.5. Relationships Part 2.''' ''If you intend to remove the gantt chart you can skip this section.''

-> If you'll be using the Gantt Chart you'll want to connect a few more things in the graph. First, create a relationship from CalendarRows to SampleEvents like this:
August 05, 2012, at 10:13 PM by 50.132.84.245 -
Changed lines 66-67 from:
-> Here, and in what follows, you don't need to import anything to do with SampleContacts or SampleProjects as you'll likely already have these things in your file. That is, you likely have a method of selecting contacts and projects and will want to use your existing method on the Event Details layout. (However, even if you do, creating Contacts and Projects values lists now will let the Event Detail layout find those value lists when you paste the layout into you file. (We also use this Projects value list on the calendar's filters: another good reason to create them now.)
to:
-> Here, and in what follows, you don't need to import anything to do with SampleContacts or SampleProjects as you'll likely already have these things in your file. That is, you likely have a method of selecting contacts and projects and will want to use your existing method on the Event Details layout. (However, even if you do have an existing method, creating Contacts and Projects values lists now will let the Event Detail layout find those value lists when you paste the layout into you file. We also use this Projects value list on the calendar's filters: another good reason to create them now.)
Changed lines 72-73 from:
-> If you have a separate table of contacts you can create a new table occurrence of that as well and name it "SampleContacts" (again, with no quotes or spaces in the name). Link this to the SampleEvents table occurrence you just created using the same field matching you use elsewhere: this is likely from the SampleEvent's contact ID to the unique ID of the contact in SampleContacts.
to:
-> If you have a separate table of contacts you can create a new table occurrence of that as well and name it "SampleContacts" (again, with no quotes or spaces in the name). Link this to the SampleEvents table occurrence you just created using the same field matching you use elsewhere: this is likely from the SampleEvent's contact ID to the unique ID of the contact in SampleContacts. Do the same with projects, if you have projects, creating a new instance of Projects named "SampleProjects" and link it to SampleEvent's project ID. You can rename these table occurrences once you're up and running.
August 05, 2012, at 10:04 PM by 50.132.84.245 -
Changed lines 56-57 from:
%center% https://www.seedcode.com/rootimages/stikipad/nextcal/graph.png
to:
%center%  https://www.seedcode.com/rootimages/stikipad/pro12/graph1.png
August 05, 2012, at 10:03 PM by 50.132.84.245 -
Changed lines 78-79 from:
%center% https://www.seedcode.com/rootimages/stikipad/nextcal/graph2.png
to:
%center% https://www.seedcode.com/rootimages/stikipad/pro12/graph1.png
August 05, 2012, at 10:00 PM by 50.132.84.245 -
Changed lines 50-51 from:
-> Import three tables into your file from SeedCode Calendar: CalendarRows, CalendarInterface, and CalendarColors. (If you're using data separation, add these tables to your interface file.)
to:
-> Import three tables into your file from SeedCode Calendar: CalendarInterface, CalendarRows,  and CalendarColors. (If you're using data separation, add these tables to your interface file.)
Added lines 60-61:
->''You'll see we also have placeholder tables for contacts, projects, and phases. You presumably already have tables in your file representing these entities, and you'll line these up later. If you don't have a contacts or projects table, and wish you did, you may want to pause this integration and take a look at %newwin% [[https://www.seedcode.com/complete | SeedCode Complete]], which already has our calendar linked to a rich contacts and project management system.''
August 05, 2012, at 09:56 PM by 50.132.84.245 -
Changed lines 28-29 from:
-> '''2.2''' Next, add the following Auto-Enter Calculated Value option to the TimeStart field in your events table:
to:
-> '''2.2''' Next, add the following Auto-Enter Calculated Value option to the TimeStart field in your events table (you can copy this here or from the definition in SampleEvents):
Deleted lines 35-36:
// v.6.13
Changed lines 40-43 from:
-->Case ( \\
Self = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ; \\
Self = Time ( 0 ; 0 ; 0 ) ; Time ( 0 ; 0 ; 1 ) ; \\
Self > Time ( 24 ; 0 ; 0 ) ; Self - Time ( 24 ; 0 ; 0 ) ;\\
to:
--> Case ( //
Self = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ; //
Self = Time ( 0 ; 0 ; 0 ) ; Time ( 0 ; 0 ; 1 ) ; //
Self > Time ( 24 ; 0 ; 0 ) ; Self - Time ( 24 ; 0 ; 0 ) + 1 ; //
Changed lines 46-48 from:

-> Make sure you '''uncheck''' the "Do not replace existing value" checkbox. This Auto-Enter option is needed if you want events to be able to start at midnight.
to:
-> Again, make sure you '''uncheck''' the "Do not replace existing value" checkbox. This Auto-Enter option is needed if you want events to be able to end at midnight.
Changed lines 52-53 from:
-> If you're using FileMaker Advanced, you can just copy and paste the three tables. If you don't have Advanced, from your file select File / Import Records... / File and then select the DayBackOnline file. Select the first of the three tables to import and for the target, select "New Table". FileMaker will create the new table and calcs for you but you'll have to come back and uncomment some of the calcs that couldn't find the items needed: come back after you've imported all three tables this way and remove the leading /* and trailing */ form your calcs.
to:
-> If you're using FileMaker Advanced, you can just copy and paste the three tables. If you don't have Advanced, from your file select File / Import Records... / File and then select the SeedCodeCalendar file. Select the first of the three tables to import and for the target, select "New Table". FileMaker will create the new table and calcs for you but you'll have to come back and uncomment some of the calcs that couldn't find the items needed: come back after you've imported all three tables this way and remove the leading /* and trailing */ form your calcs.
August 05, 2012, at 09:54 PM by 50.132.84.245 -
Deleted lines 18-19:
-> Lastly, while it may be tempting for some of you to open your file in one version of FileMaker and ours in another, to make copying and pasting a little faster, this will actually cause problems when the scripts are brought over. So while the calendar works great in FM10 or FM11, do the integration work in one version or the other: don't copy and paste between them.
Changed lines 23-27 from:
--> z_sc_TimestampEndCalc
--> z_sc_TimestampStartCalc

-> Edit the definitions for these calcs, removing any leading / trailing comment tags if you pasted the fields in using FileMaker Advanced (that is, remove the /* and */ from the beginning and end of the calc). Then replace the DateStart, TimeStart, etc. fields in these calculations with the relevant fields from your events table. Make sure both calcs return the form "timestamp" and that both are indexed.
to:
--> zscTimestampStartCalcNum
--> zscTimestampEndCalcNum

-> Edit the definitions for these calcs, removing any leading / trailing comment tags if you pasted the fields in using FileMaker Advanced (that is, remove the /* and */ from the beginning and end of the calc). Then replace the DateStart, TimeStart, etc. fields refrenced in these calculations with the relevant fields from your events table. Make sure both calcs return the form "number" and that both are indexed.
Changed lines 31-32 from:
Self = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ;\\
Self = Time ( 0 ; 0 ; 0 ) ; Time ( 0 ; 0 ; 1 ) ;\\
to:
Self = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ; \\
Self = Time ( 0 ; 0 ; 0 ) ; Time ( 0 ; 0 ; 1 ) ; \\
Self > Time ( 24 ; 0 ; 0 ) ; Self - Time ( 24 ; 0 ; 0 ) + 1 ;
\\
Added lines 36-37:
// v.6.13
April 18, 2012, at 01:20 PM by 166.137.10.13 -
Added lines 60-61:
-> If you'd like to use the calendar's [[To-Do List]] and don't have your own To-Do table already, you can import our ToDoList table into your own file at this time as well. Leave it named "ToDoList" and that will keep things easier in the following steps.
Added lines 122-123:
-> If you're using the [[To-Do List]] add the To-Do Details and To-Do List layouts as well.
March 14, 2012, at 02:28 PM by 50.132.84.245 -
Changed lines 179-180 from:
-> Rename your Sample Events table occurrence to something that makes more sense for you. And add the script "Upon Opening" to your file's opening script, removing the go to layout stuff if you'd like.
to:
-> Rename your Sample Events table occurrence to something that makes more sense for you. And add the script "Upon Opening" to your file's opening script, removing the go to layout stuff if you'd like. If you're using multiple windows or renaming windows in your own upon opening script, you may want to run our Upon Opening routine the first time your users open the calendar in a new window rather than at the beginning. 
December 02, 2011, at 01:00 AM by 50.132.84.245 -
Changed lines 106-107 from:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required). This is most easily done by creating the first layout listed below and duplicating it to create the others. Create the layout and then visit Layout Setup and uncheck the box beside "Show field frames when record is active". Also uncheck the box to enable QuickFind if you're using FileMaker 11. (If you want to search the calendar using QuickFind you can leave this enabled on the EventList layout, or use %newwin% [[https://www.seedcode.com/cp-app/ste_cat/fmsearchresults | fmSearchResults]] to extend QuickFind. Do this after you've followed these instructions and are up and running.) Keep duplicating and renaming layouts making sure to switch "Show records from" to match the associated table shown in the list below.
to:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required). This is most easily done by creating the first layout listed below, deleting the header and footer part, and duplicating it to create the others. Create the layout and then visit Layout Setup and uncheck the box beside "Show field frames when record is active". Also uncheck the box to enable QuickFind if you're using FileMaker 11. (If you want to search the calendar using QuickFind you can leave this enabled on the EventList layout, or use %newwin% [[https://www.seedcode.com/cp-app/ste_cat/fmsearchresults | fmSearchResults]] to extend QuickFind. Do this after you've followed these instructions and are up and running.) Keep duplicating and renaming layouts making sure to switch "Show records from" to match the associated table shown in the list below.
Changed lines 112-113 from:
-> Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them.
to:
-> Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and that the headers and footers are deleted from each.
December 01, 2011, at 06:05 PM by 50.132.84.245 -
Changed lines 62-65 from:
-> Open SeedCode Calendar and recreate the 5 value lists from our calendar in your file (leaving "Contacts" out). Feel free to use your list of statuses and resources, but rename them to the names we're using in SeedCode Calendar: you can name them back later. The other values lists need to stay as they are, though you can feel free to change the time formats in "Calendar Times" to suit your tastes. You might want to do that later though, once you have this up and running.

-> Here, and in what follows, you don't need to import anything to do with SampleContacts as you'll likely already have these things in your file.
to:
-> Open SeedCode Calendar and recreate the 7 value lists from our calendar in your file. Feel free to use your list of statuses and resources, but rename them to the names we're using in SeedCode Calendar: you can name them back later. The other values lists need to stay as they are, though you can feel free to change the time formats in "Calendar Times" to suit your tastes. You might want to do that later though, once you have this up and running.

-> Here, and in what follows, you don't need to import anything to do with SampleContacts or SampleProjects as you'll likely already have these things in your file. That is, you likely have a method of selecting contacts and projects and will want to use your existing method on the Event Details layout. (However, even if you do, creating Contacts and Projects values lists now will let the Event Detail layout find those value lists when you paste the layout into you file. (We also use this Projects value list on the calendar's filters: another good reason to create them now.)
Added lines 167-168:
-> Edit the script "Create Edit Delete Event..." and you'll see a few fields "missing". Point these at the fields in your events table with the same name. You can tell which field to use from the names of the variable we're setting into them.
Changed lines 32-33 from:
--> If ( Self = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ; Self )
to:
--> Case ( \\
Self = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ;\\
Self = Time ( 0 ; 0 ; 0 ) ; Time ( 0 ; 0 ; 1 ) ;\\

Self )
Added line 43:
Self = Time ( 0 ; 0 ; 0 ) ; Time ( 0 ; 0 ; 1 ) ; \\
May 14, 2011, at 10:57 PM by 76.22.74.86 -
Added lines 165-170:
-> A couple tips:

--> Events with just a single date should have a start date: if your event has just an end date the calendar will fail. The same goes for times: if there is only one time, make it the start time.

--> Don't use calcs for things like the dates, times, or resources. The calendar wants to edit these values when you drag items around, and it can't edit calcs. Use auto-enter calculations instead if you must.

Changed lines 88-99 from:
to:
-> Once your section of the graph looks like ours above, you can create a couple new fields in your Projects table, and in your Phases table if you're using Phases.

--> In Projects create the calc "ProjectDateEarliestEventCalc" returning the type Date equal to: Min ( SampleEvents::DateStart )

--> Also in Projects create the calc "ProjectDateLatestEventCalc" returning the type Date equal to: Max ( Max ( SampleEvents::DateEnd ) ; Max ( SampleEvents::DateStart ) )

--> In Phases (if you're using Phases) create the calc "PhaseDateEarliestEventCalc" returning the type Date equal to: Min ( SampleEvents::DateStart )

--> Also in Phases create the calc "PhaseDateLatestEventCalc" returning the type Date equal to: Max ( Max ( SampleEvents::DateEnd ) ; Max ( SampleEvents::DateStart ) )

--> Finally, in SampleEvents, create a new number field called "z_LinkedWithinProject"

Changed lines 111-112 from:
->
to:
-> If you're using the gantt chart, edit the script "Record Gantt Chart Field Names..." and follow the instructions in each SetVariable line to point the script at the Project and Phase fields in your tables. Some lines may already be correct if you've named your fields the same way we have. You may need to create a couple of fields in your Project's table, and create the field "z_LinkedWithinProject" in SampleEvents if you haven't already. While Phases aren't required-- you can skip the phase fields if you're not using phases, all 3 project fields and the one field from SampleEvents mentioned in this script are required.
Changed lines 70-73 from:
-> '''6.1 Relationships Part 1.''' 

->
Staying on the Relationships tab, link "CalendarRows" to "CalendarInterface" to "CalendarColors" as shown below. Double check that the table occurrence names match what we have in the sample file.
to:
-> '''6.1 Relationships Part 1.''' Staying on the Relationships tab, link "CalendarRows" to "CalendarInterface" to "CalendarColors" as shown below. Double check that the table occurrence names match what we have in the sample file.
Changed lines 76-79 from:
-> '''6.5. Relationships Part 2.''' 

->
''The [[gantt chart]] was introduced in version 5.6 of the calendar. If you're not using the gantt chart you can skip this section.''
to:
-> '''6.5. Relationships Part 2.''' ''The [[gantt chart]] was introduced in version 5.6 of the calendar. If you're not using the gantt chart you can skip this section.''
Changed lines 68-69 from:
'''6. Relationships
to:
'''6. Relationships'''
Changed lines 80-81 from:
''The [[gantt chart]] was introduced in version 5.6 of the calendar. If you're not using the gantt chart you can skip this section.''
to:
-> ''The [[gantt chart]] was introduced in version 5.6 of the calendar. If you're not using the gantt chart you can skip this section.''
Changed lines 68-69 from:
'''6. Relationships Part 1.'''
to:
'''6. Relationships

-> '''6.1
Relationships Part 1.'''
Changed lines 78-81 from:
'''6.5. Relationships Part 2.'''

''The gantt chart was introduced in version 5.6 of the calendar. If you're not using the gantt chart, or don't have Projects in your file, you can skip this section.''
to:
-> '''6.5. Relationships Part 2.'''

''The [[gantt chart]] was introduced in version 5.6 of the calendar. If you're not using the gantt chart you can skip this section.''
Added lines 115-116:
->
Changed lines 119-120 from:
-> Just as you needed to click on fields on Event Details and point them at the proper fields in your table, you'll need to do the same to the Event List layout and to the Gantt Chart tab of the Calendar layouts. Navigating to the gantt tab means moving one of our button bars: you'll find notes about how to get to this here: %newwin% [[CalendarTabs | working with the calendar tabs]].
to:
-> Just as you needed to click on fields on Event Details and point them at the proper fields in your table, you'll need to do the same to the Event List layout and to the Gantt Chart tab of the Calendar layouts. ''If you're not using the gantt charts, skip on to step 10.''

->
Navigating to the gantt tab means moving one of our button bars: you'll find notes about how to get to this here: %newwin% [[CalendarTabs | working with the calendar tabs]].
Added lines 119-126:
-> Just as you needed to click on fields on Event Details and point them at the proper fields in your table, you'll need to do the same to the Event List layout and to the Gantt Chart tab of the Calendar layouts. Navigating to the gantt tab means moving one of our button bars: you'll find notes about how to get to this here: %newwin% [[CalendarTabs | working with the calendar tabs]].

-> On the gantt tab you only need to edit the three fields to the left of the vertical black line. These fields are stacked on top of each other, so click on the top one, dragging it down and out of the way: hold the shift key down while dragging to you don't move the field to the left or right. Do this again with the next field until your layout looks like this:

%center% https://www.seedcode.com/rootimages/stikipad/nextcal/ganttfields.png

-> It doesn't matter in which order you drag the fields, but you'll point them at their correct fields in your table starting with the one that is furthest to the left (that is the lowest one in the illustration above). Point that field at the name of your Project in SampleProjects. Point the next field in from the left at your Phase's name from SamplePhases if you have phases: if you don't have phases, delete the field. Finally point the one starting furthest to the right at the Summary field in your Sample Events table. Then move the two fields back up to their original positions.

Changed lines 138-139 from:
-> '''11.2 Sort your records.''' Edit the script "Sort FileMaker Records..." and follow the instructions to sort your records by date / time ascending, editing the sort step there to use fields from your events table.
to:
-> '''11.2 Sort your records.''' Edit the script "Sort FileMaker Records..." and follow the instructions to sort your records by date / time ascending, editing the sort step there to use fields from your events table.

-> If you're using the gantt chart, edit the script "Sort FileMaker Records for Gantt Chart..." following the instructions in the script's comments.

Changed lines 78-79 from:
-> ''The gantt chart was introduced in version 5.6 of the calendar. If you're not using the gantt chart, or don't have Projects in your file, you can skip this section.''
to:
''The gantt chart was introduced in version 5.6 of the calendar. If you're not using the gantt chart, or don't have Projects in your file, you can skip this section.''
Added line 81:
Added line 83:
Changed lines 68-69 from:
'''6. Relationships.'''
to:
'''6. Relationships Part 1.'''
Added lines 76-88:
'''6.5. Relationships Part 2.'''

-> ''The gantt chart was introduced in version 5.6 of the calendar. If you're not using the gantt chart, or don't have Projects in your file, you can skip this section.''

-> If you'll be using the Gantt Charts you'll want to connect a few more things in the graph. First, create a relationship from CalendarRows to SampleEvents like this:
--> CalendarEventUIDCalc_FirstValue = _id
-> Where _id is the primary key (the unique ID) in your events table. Then attach SampleEvents to your Contacts, Projects, and possibly your Phases table occurrences, as shown here:

%center% https://www.seedcode.com/rootimages/stikipad/nextcal/ganttgraph.png

-> It probably make sense to create new instances of these to attach to SampleEvents, but you don't have to. You may, however, want to rename your table occurrences to "Sample..." for now so that items pasted in later will line up. If you don't have a Phases table, don't worry; phases are completely optional.

August 09, 2010, at 02:49 AM by 76.22.123.157 -
Changed lines 48-49 from:
-> Import three tables into your file from SeedCode Calendar: CalendarRows, CalendarInterface, and CalendarColors. If you were ever wondering why people bought FileMaker Advanced, this is why, though you can certainly do it by hand. (If you don't have Advanced we'd be happy to complete this step for you, just send us your file.) If you do it by hand, start with regular fields first, and the do calcs, starting with CalendarInterface, the add CalendarRow, and the CalendarColors. (If you're using data separation, add these tables to your interface file.)
to:
-> Import three tables into your file from SeedCode Calendar: CalendarRows, CalendarInterface, and CalendarColors. (If you're using data separation, add these tables to your interface file.)

-> If
you're using FileMaker Advanced, you can just copy and paste the three tables. If you don't have Advanced, from your file select File / Import Records... / File and then select the DayBackOnline file. Select the first of the three tables to import and for the target, select "New Table". FileMaker will create the new table and calcs for you but you'll have to come back and uncomment some of the calcs that couldn't find the items needed: come back after you've imported all three tables this way and remove the leading /* and trailing */ form your calcs.

-> If you don't have Advanced, and that sounds like too much, we'd be happy to complete this step for you, just send us your file.

May 26, 2010, at 03:10 PM by 76.22.123.157 -
Changed lines 54-55 from:
-> Open SeedCode Calendar and recreate the 5 value lists in your file (leaving "Contacts" out). Feel free to use your list of statuses and resources, but rename them to the names we're using in SeedCode Calendar: you can name them back later. The other values lists need to stay as they are, though you can feel free to change the time formats in "Calendar Times" to suit your tastes. You might want to do that later though, once you have this up and running.
to:
-> Open SeedCode Calendar and recreate the 5 value lists from our calendar in your file (leaving "Contacts" out). Feel free to use your list of statuses and resources, but rename them to the names we're using in SeedCode Calendar: you can name them back later. The other values lists need to stay as they are, though you can feel free to change the time formats in "Calendar Times" to suit your tastes. You might want to do that later though, once you have this up and running.
May 09, 2010, at 10:03 PM by 76.22.123.157 -
Changed lines 1-2 from:
!! Pasting SeedCode Calendar into your File.
to:
!! Integration Options.
Changed lines 9-10 from:
!! Step-by-Step Instructions.
to:
!! Step-by-Step Instructions: Pasting SeedCode Calendar into your File.
May 08, 2010, at 11:17 PM by 76.22.123.157 -
Added lines 9-10:
!! Step-by-Step Instructions.
May 08, 2010, at 11:17 PM by 76.22.123.157 -
Changed lines 1-4 from:
!! Adding SeedCode Calendar to your File: the Quick Version.

Most folks will paste SeedCode Calendar into their file and use an events table they already have for the events they want to see in the calendar. These instructions are for them. If you want to use the Sample Events table in SeedCode Calendar as
your events table, just import it into your file in step 2 below and skip step 5.
to:
!! Pasting SeedCode Calendar into your File.

Most folks will paste SeedCode Calendar into their file and use an events table they already have for the events they want to see in the calendar.

If you don't need to have the calendar "in" your file, you can still link the two files, pointing the calendar at
your events table instead of the SampleEvents table it comes with. Linking in this way is much faster but means you'll have two files instead of one. (The chief disadvantage of this is that you have to have the same accounts and passwords in each file, unless you set the calendar file to auto-open with its own low access password for everyone.)

If this sounds like it might be for you, follow our instructions for the [[Quick Integration]]
.
Added lines 15-16:
-> If you want to use the Sample Events table in SeedCode Calendar as your events table, instead of a table you already have, just import it into your file in step 2 below and skip step 5.
May 08, 2010, at 11:11 PM by 76.22.123.157 -
Deleted lines 4-5:
''Note. While it may be tempting for some of you to open your file in one version of FileMaker and ours in another, to make copying and pasting a little faster, this will actually cause problems when the scripts are brought over. So while the calendar works great in FM10 or FM11, do the integration work in one version or the other: don't copy and paste between them.''
Added lines 11-12:
-> Lastly, while it may be tempting for some of you to open your file in one version of FileMaker and ours in another, to make copying and pasting a little faster, this will actually cause problems when the scripts are brought over. So while the calendar works great in FM10 or FM11, do the integration work in one version or the other: don't copy and paste between them.
May 03, 2010, at 06:14 PM by 67.171.26.249 -
Changed lines 84-85 from:
-> However, if any scripts are reported as being "renamed" because of a conflict, quickly scan the imported scripts for named ending "2" and correct them. For example, the calendar has a script called "Upon Opening". If you already have one with that name ours will get imported as "Upon Opening 2". To fix this rename yours to something like "Upon Opening Main" and then rename ours to "Upon Opening". Our scripts must have the same names as they do in the SeedCode Calendar file for the following step to work.
to:
-> However, if any scripts are reported as being "renamed" because of a conflict, quickly scan the imported scripts for names ending "2" and correct them. For example, the calendar has a script called "Upon Opening". If you already have one with that name ours will get imported as "Upon Opening 2". To fix this '''rename yours''' to something like "Upon Opening Main" and then rename ours to "Upon Opening". Our scripts must have the same names as they do in the SeedCode Calendar file for the following step to work.
April 14, 2010, at 03:26 PM by 76.22.123.157 -
Added lines 5-6:
''Note. While it may be tempting for some of you to open your file in one version of FileMaker and ours in another, to make copying and pasting a little faster, this will actually cause problems when the scripts are brought over. So while the calendar works great in FM10 or FM11, do the integration work in one version or the other: don't copy and paste between them.''
April 08, 2010, at 06:40 PM by 76.22.123.157 -
Changed lines 38-39 from:
-> Import three tables into your file from SeedCode Calendar: CalendarRows, CalendarInterface, and CalendarColors. If you were ever wondering why people bought FileMaker Advanced, this is why, though you can certainly do it by hand. (If you don't have Advanced we'd be happy to complete this step for you, just send us your file.) If you do it by hand, start with regular fields first, and the do calcs, starting with CalendarInterface, the add CalendarRow, and the CalendarColors.
to:
-> Import three tables into your file from SeedCode Calendar: CalendarRows, CalendarInterface, and CalendarColors. If you were ever wondering why people bought FileMaker Advanced, this is why, though you can certainly do it by hand. (If you don't have Advanced we'd be happy to complete this step for you, just send us your file.) If you do it by hand, start with regular fields first, and the do calcs, starting with CalendarInterface, the add CalendarRow, and the CalendarColors. (If you're using data separation, add these tables to your interface file.)
March 14, 2010, at 12:07 AM by 76.22.123.157 -
Changed lines 94-102 from:
-> Layout: Calendar (1 trigger)
-> Trigger: OnRecordLoad (in Browse and Find Mode)
-> Script: "Load Calendar Layout"
-> (Do this on each of the four calendar layouts.)

-> Layout: Event Details (1 trigger)
-> Trigger: OnRecordLoad (in Browse Mode)
-> Script: "On Event Record Load"
to:
--> Layout: Calendar (1 trigger)
--> Trigger: OnRecordLoad (in Browse and Find Mode)
--> Script: "Load Calendar Layout"
--> (Do this on each of the four calendar layouts.)

--> Layout: Event Details (1 trigger)
--> Trigger: OnRecordLoad (in Browse Mode)
--> Script: "On Event Record Load"

--> Return to the Calendar Home layout when you're done and enter Browse Mode.

March 14, 2010, at 12:04 AM by 76.22.123.157 -
Changed lines 95-96 from:
-> Trigger: OnRecordLoad - "Load Calendar Layout" (in Browse and Find Mode)
to:
-> Trigger: OnRecordLoad (in Browse and Find Mode)
-> Script: "Load Calendar Layout"
Changed lines 100-101 from:
-> Trigger: OnRecordLoad - "On Event Record Load"
to:
-> Trigger: OnRecordLoad (in Browse Mode)
-> Script:
"On Event Record Load"
March 13, 2010, at 10:12 PM by 76.22.123.157 -
Changed lines 86-89 from:
-> Now copy the layout contents from each layout in SeedCode Calendar and paste them into the layout of the same name in your file. And yes, we do need the contents of "Calendar Records" on that layout. The contents of "Developer" are optional. You'll be warned that you'll be increasing the size of each layout; that's OK.

-> When you get to Event Details feel free to edit this layout as you see fit, adding your own fields and buttons. Just be sure to keep
the following 3 objects: the "repeat" button, the "show repts..." button below it, and the large "close..." button at the bottom of the screen.
to:
-> Now copy the layout contents from each layout in SeedCode Calendar and paste them into the layout of the same name in your file. Do every layout, including Calendar Rows and Calendar Color Records. You'll be warned that you'll be increasing the size of each layout; that's OK.

-> When you get to Event Details feel free to edit this layout as you see fit, adding your own fields and buttons. Just be sure to keep the following 3 objects: the "repeat" button,
the "show repts..." button below it, and the large "close..." button at the bottom of the screen. You can come back and edit this layout later, for now, just get the Summary, Date, and Time fields lined up with the relevant fields in your events table.
March 13, 2010, at 10:08 PM by 76.22.123.157 -
March 13, 2010, at 10:08 PM by 76.22.123.157 -
Added lines 82-83:
-> However, if any scripts are reported as being "renamed" because of a conflict, quickly scan the imported scripts for named ending "2" and correct them. For example, the calendar has a script called "Upon Opening". If you already have one with that name ours will get imported as "Upon Opening 2". To fix this rename yours to something like "Upon Opening Main" and then rename ours to "Upon Opening". Our scripts must have the same names as they do in the SeedCode Calendar file for the following step to work.
March 13, 2010, at 09:56 PM by 76.22.123.157 -
Changed lines 64-65 from:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required). This is most easily done by creating the first layout listed below and duplicating it to create the others. Create the layout and then visit Layout Setup and uncheck the box beside "Show field frames when record is active". Also uncheck the box to enable QuickFind if you're using FileMaker 11. (If you want to search the calendar using QuickFind you can leave this enabled on the EventList layout, or use %newwin% [[https://www.seedcode.com/cp-app/ste_cat/fmsearchresults | fmSearchResults]] to extend QuickFind. Do this after you've followed these instructions and are up and running.) Keep duplicating and renaming layouts making sure to switch "Show records from" to match the table
to:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required). This is most easily done by creating the first layout listed below and duplicating it to create the others. Create the layout and then visit Layout Setup and uncheck the box beside "Show field frames when record is active". Also uncheck the box to enable QuickFind if you're using FileMaker 11. (If you want to search the calendar using QuickFind you can leave this enabled on the EventList layout, or use %newwin% [[https://www.seedcode.com/cp-app/ste_cat/fmsearchresults | fmSearchResults]] to extend QuickFind. Do this after you've followed these instructions and are up and running.) Keep duplicating and renaming layouts making sure to switch "Show records from" to match the associated table shown in the list below.
March 13, 2010, at 09:56 PM by 76.22.123.157 -
Changed lines 64-65 from:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required). This is most easily done by creating the first layout listed below and duplicating it to create the others. Create the layout and then visit Layout Setup and uncheck the box beside "Show field frames when record is active". Also uncheck the box to enable QuickFind if you're using FileMaker 11. (If you want to search the calendar using QuickFind you can leave this enabled on the EventList layout, or use %newwin% [[https://www.seedcode.com/cp-app/ste_cat/fmsearchresults | fmSearchResults]] to extend QuickFind. Do this after you've followed these instructions and are up and running.)
to:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required). This is most easily done by creating the first layout listed below and duplicating it to create the others. Create the layout and then visit Layout Setup and uncheck the box beside "Show field frames when record is active". Also uncheck the box to enable QuickFind if you're using FileMaker 11. (If you want to search the calendar using QuickFind you can leave this enabled on the EventList layout, or use %newwin% [[https://www.seedcode.com/cp-app/ste_cat/fmsearchresults | fmSearchResults]] to extend QuickFind. Do this after you've followed these instructions and are up and running.) Keep duplicating and renaming layouts making sure to switch "Show records from" to match the table
March 13, 2010, at 09:54 PM by 76.22.123.157 -
Changed lines 64-65 from:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required). Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Visit Layout Setup and uncheck the box beside "Show field frames when record is active". Also uncheck the box to enable QuickFind if you're using FileMaker 11. (If you want to search the calendar using QuickFind you can leave this enabled on the EventList layout, or use %newwin% [[https://www.seedcode.com/cp-app/ste_cat/fmsearchresults | fmSearchResults]] to extend QuickFind. Do this after you've followed these instructions and are up and running.)
to:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required). This is most easily done by creating the first layout listed below and duplicating it to create the others. Create the layout and then visit Layout Setup and uncheck the box beside "Show field frames when record is active". Also uncheck the box to enable QuickFind if you're using FileMaker 11. (If you want to search the calendar using QuickFind you can leave this enabled on the EventList layout, or use %newwin% [[https://www.seedcode.com/cp-app/ste_cat/fmsearchresults | fmSearchResults]] to extend QuickFind. Do this after you've followed these instructions and are up and running.)
Changed lines 70-71 from:
-> And delete the default layouts created when you imported tables in step 3.
to:
-> Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them.

-> Finally,
delete the default layouts created when you imported tables in step 3.
March 13, 2010, at 09:51 PM by 76.22.123.157 -
Changed lines 64-65 from:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required). Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Visit Layout Setup and uncheck the box beside "Show field frames when record is active". Again, you don't need to add the contact layouts unless you don't have any of your own.
to:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required). Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Visit Layout Setup and uncheck the box beside "Show field frames when record is active". Also uncheck the box to enable QuickFind if you're using FileMaker 11. (If you want to search the calendar using QuickFind you can leave this enabled on the EventList layout, or use %newwin% [[https://www.seedcode.com/cp-app/ste_cat/fmsearchresults | fmSearchResults]] to extend QuickFind. Do this after you've followed these instructions and are up and running.)

->
Again, you don't need to add the contact layouts unless you don't have any of your own.
March 13, 2010, at 09:47 PM by 76.22.123.157 -
Changed lines 64-65 from:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required). Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Again, you don't need to import the contact layouts unless you don't have any of your own.
to:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required). Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Visit Layout Setup and uncheck the box beside "Show field frames when record is active". Again, you don't need to add the contact layouts unless you don't have any of your own.
March 13, 2010, at 09:44 PM by 76.22.123.157 -
Changed lines 60-61 from:
-> At this point, if you want to show event colors in list view as we do in the Event List or Event Detail layouts, copy our field "z_ColorCalc" from Sample Events and add it to your events table mapping our field "status" to the equivalent field in your table: this is the field we used to color code events in the calendar.
to:
-> At this point, if you want to show event colors in list view as we do in the Event List or Event Detail layouts, copy our field "z_ColorCalc" from Sample Events and add it to your events table. Remove the /* and */ from the beginning and end of the calc and replace our use of the field "status" with the equivalent field in your events table: this is the field we used to color code events in the calendar.
March 13, 2010, at 09:35 PM by 76.22.123.157 -
Changed lines 44-45 from:
-> Open SeedCode Calendar and recreate the 5 value lists in your file (leaving "Contacts" out). Feel free to use your list of statuses and resources. The other values lists need to stay as they are, though you can feel free to change the time formats in "Calendar Times" to suit your tastes. You might want to do that later though, once you have this up and running.
to:
-> Open SeedCode Calendar and recreate the 5 value lists in your file (leaving "Contacts" out). Feel free to use your list of statuses and resources, but rename them to the names we're using in SeedCode Calendar: you can name them back later. The other values lists need to stay as they are, though you can feel free to change the time formats in "Calendar Times" to suit your tastes. You might want to do that later though, once you have this up and running.
March 13, 2010, at 09:33 PM by 76.22.123.157 -
Changed lines 18-19 from:
-> Edit the definitions for these calcs, removing any leading / trailing comment tags if you pasted the fields in using FileMaker Advanced (that is, remove the /* and */ from the beginning and end of the calc. Then replace the DateStart, TimeStart, etc. fields in these calculations with the relevant fields from your events table. Make sure both calcs return the form "timestamp" and that both are indexed.
to:
-> Edit the definitions for these calcs, removing any leading / trailing comment tags if you pasted the fields in using FileMaker Advanced (that is, remove the /* and */ from the beginning and end of the calc). Then replace the DateStart, TimeStart, etc. fields in these calculations with the relevant fields from your events table. Make sure both calcs return the form "timestamp" and that both are indexed.
March 13, 2010, at 07:51 PM by 76.22.123.157 -
Added lines 52-53:
-> If you have a separate table of contacts you can create a new table occurrence of that as well and name it "SampleContacts" (again, with no quotes or spaces in the name). Link this to the SampleEvents table occurrence you just created using the same field matching you use elsewhere: this is likely from the SampleEvent's contact ID to the unique ID of the contact in SampleContacts.
March 13, 2010, at 07:48 PM by 76.22.123.157 -
Changed lines 54-55 from:
-> Staying on the Relationships tab, link "CalendarRows" to "CalendarInterface" to "CalendarColors" as shown on the Relationships tab in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file.
to:
-> Staying on the Relationships tab, link "CalendarRows" to "CalendarInterface" to "CalendarColors" as shown below. Double check that the table occurrence names match what we have in the sample file.
March 13, 2010, at 07:48 PM by 76.22.123.157 -
Changed lines 50-51 from:
-> Create a new occurrence of your events table (the table that has the records you want to see on the calendar) and name it "SampleEvents" (make sure there are no spaces in the table occurrence name). You can change this name later.
to:
-> Select File / Manage / Database and navigate to the Relationships tab where you can see the "relationship graph" for your file. Click the little green plus button in the lower left to create a new occurrence of your events table (the table that has the records you want to see on the calendar) and name it "SampleEvents" (make sure there are no spaces in the table occurrence name). You can change this name later.
Changed lines 54-55 from:
-> On your relationship graph, link "CalendarRows" to "CalendarInterface" to "CalendarColors" as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file.
to:
-> Staying on the Relationships tab, link "CalendarRows" to "CalendarInterface" to "CalendarColors" as shown on the Relationships tab in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file.

%center% https://www.seedcode.com/rootimages/stikipad/nextcal/graph2.png

Deleted lines 59-60:
%center% https://www.seedcode.com/rootimages/stikipad/nextcal/graph2.png
February 26, 2010, at 02:56 PM by 76.22.123.157 -
Changed lines 18-19 from:
-> Edit the definitions for these calcs, removing any leading / trailing comment tags if you pasted the fields in using FielMaker Advanced (that is, remove the /* and */ from the beginning and end of the calc. Then replace the DateStart, TimeStart, etc. fields in these calculations with the relevant fields from your events table. Make sure both calcs return the form "timestamp" and that both are indexed.
to:
-> Edit the definitions for these calcs, removing any leading / trailing comment tags if you pasted the fields in using FileMaker Advanced (that is, remove the /* and */ from the beginning and end of the calc. Then replace the DateStart, TimeStart, etc. fields in these calculations with the relevant fields from your events table. Make sure both calcs return the form "timestamp" and that both are indexed.
February 25, 2010, at 04:51 PM by 76.22.123.157 -
Changed lines 38-39 from:
-> Import three tables into your file from SeedCode Calendar: CalendarRows, CalendarInterface, and CalendarColors. If you were ever wondering why people bought FileMaker Advanced, this is why, though you can certainly do it by hand. (If you don't have Advanced we'd be happy to complete this step for you, just send us your file.) Start with CalendarInterface, the add CalendarRow, and the CalendarColors.
to:
-> Import three tables into your file from SeedCode Calendar: CalendarRows, CalendarInterface, and CalendarColors. If you were ever wondering why people bought FileMaker Advanced, this is why, though you can certainly do it by hand. (If you don't have Advanced we'd be happy to complete this step for you, just send us your file.) If you do it by hand, start with regular fields first, and the do calcs, starting with CalendarInterface, the add CalendarRow, and the CalendarColors.
February 25, 2010, at 04:49 PM by 76.22.123.157 -
Changed lines 38-39 from:
-> Import three tables into your file from SeedCode Calendar: CalendarRows, CalendarInterface, and CalendarColors. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us your file.
to:
-> Import three tables into your file from SeedCode Calendar: CalendarRows, CalendarInterface, and CalendarColors. If you were ever wondering why people bought FileMaker Advanced, this is why, though you can certainly do it by hand. (If you don't have Advanced we'd be happy to complete this step for you, just send us your file.) Start with CalendarInterface, the add CalendarRow, and the CalendarColors.
February 25, 2010, at 04:48 PM by 76.22.123.157 -
Changed lines 26-27 from:
-> ''2.23'' Now add the following Auto-Enter Calculated Value option to the TimeEnd field in your events table:
to:
-> '''2.3''' Now add the following Auto-Enter Calculated Value option to the TimeEnd field in your events table:
February 25, 2010, at 04:48 PM by 76.22.123.157 -
Changed lines 26-27 from:
-> '''2.23'' Now add the following Auto-Enter Calculated Value option to the TimeEnd field in your events table:
to:
-> ''2.23'' Now add the following Auto-Enter Calculated Value option to the TimeEnd field in your events table:
February 25, 2010, at 04:47 PM by 76.22.123.157 -
Added lines 26-35:
-> '''2.23'' Now add the following Auto-Enter Calculated Value option to the TimeEnd field in your events table:

-->Case ( \\
Self = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ; \\
Self > Time ( 24 ; 0 ; 0 ) ; Self - Time ( 24 ; 0 ; 0 ) ;\\
Self )


-> Make sure you '''uncheck''' the "Do not replace existing value" checkbox. This Auto-Enter option is needed if you want events to be able to start at midnight.

February 25, 2010, at 04:45 PM by 76.22.123.157 -
Changed lines 24-25 from:
-> Make sure you uncheck the "Do not replace existing value" checkbox. This Auto-Enter option is needed if you want events to be able to start at midnight.
to:
-> Make sure you '''uncheck''' the "Do not replace existing value" checkbox. This Auto-Enter option is needed if you want events to be able to start at midnight.
February 24, 2010, at 03:12 PM by 76.22.123.157 -
Changed lines 52-57 from:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Again, you don't need to import the contact layouts unless you don't have any of your own.

-> You may want to create the separator layouts we have as well (these are based on CalendarInterface) but that is just cosmetic
.

-> Delete the default layouts created when you imported tables in step 3.
to:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required). Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Again, you don't need to import the contact layouts unless you don't have any of your own.

-> You may want to create the separator layouts we have as well (these are based on CalendarInterface) but that is just cosmetic. Make sure each layout is based on the table occurrence shown below
.

-> And delete the default layouts created when you imported tables in step 3.
February 24, 2010, at 03:11 PM by 76.22.123.157 -
Changed lines 52-53 from:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Again, you don't need to import the contact layouts unless you don't have any of your own.
to:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users in the layouts menu, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Again, you don't need to import the contact layouts unless you don't have any of your own.
February 24, 2010, at 03:10 PM by 76.22.123.157 -
Changed lines 52-53 from:
-> Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Again, you don't need to import the contact layouts unless you don't have any of your own.
to:
-> Create a few blank layouts in your file. (We'll paste in content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Again, you don't need to import the contact layouts unless you don't have any of your own.
February 03, 2010, at 10:33 PM by 76.22.123.157 -
Changed line 76 from:
-> Layout: Calendar (2 triggers)
to:
-> Layout: Calendar (1 trigger)
February 03, 2010, at 02:41 AM by 76.22.123.157 -
Changed lines 54-55 from:
-> You may want to create the separator layouts we have as well (these are based on Calendar Events) but that is just cosmetic.
to:
-> You may want to create the separator layouts we have as well (these are based on CalendarInterface) but that is just cosmetic.
Changed lines 58-59 from:
> > screen shot of layout list
to:
%center% https://www.seedcode.com/rootimages/stikipad/nextcal/layoutlist.png
February 03, 2010, at 02:39 AM by 76.22.123.157 -
Changed lines 48-49 from:
> > screen shot of graph
to:
%center% https://www.seedcode.com/rootimages/stikipad/nextcal/graph2.png
February 03, 2010, at 02:37 AM by 76.22.123.157 -
February 03, 2010, at 02:37 AM by 76.22.123.157 -
Changed lines 28-29 from:
-> Import three tables into your file from SeedCode Calendar: Calendar Rows, Calendar Interface, and Calendar Colors. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us your file.
to:
-> Import three tables into your file from SeedCode Calendar: CalendarRows, CalendarInterface, and CalendarColors. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us your file.
Changed lines 44-45 from:
-> On your relationship graph, link "CalendarRows" to "CalendarInterface" as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file.
to:
-> On your relationship graph, link "CalendarRows" to "CalendarInterface" to "CalendarColors" as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file.
February 03, 2010, at 02:36 AM by 76.22.123.157 -
Changed lines 34-35 from:
-> Open SeedCode Calendar and recreate the 5 value lists in your file. Feel free to use your list of statuses and resources. The other values lists need to stay as they are, though you can feel free to change the time formats in "Calendar Times" to suit your tastes. You might want to do that later though, once you have this up and running.
to:
-> Open SeedCode Calendar and recreate the 5 value lists in your file (leaving "Contacts" out). Feel free to use your list of statuses and resources. The other values lists need to stay as they are, though you can feel free to change the time formats in "Calendar Times" to suit your tastes. You might want to do that later though, once you have this up and running.
February 03, 2010, at 02:34 AM by 76.22.123.157 -
Changed lines 28-29 from:
-> Import two tables into your file from SeedCode Calendar: Calendar Rows and Calendar Interface. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us your file.
to:
-> Import three tables into your file from SeedCode Calendar: Calendar Rows, Calendar Interface, and Calendar Colors. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us your file.
February 03, 2010, at 02:33 AM by 76.22.123.157 -
Changed lines 30-31 from:
%center% https://www.seedcode.com/rootimages/stikipad/calnext/graph.png
to:
%center% https://www.seedcode.com/rootimages/stikipad/nextcal/graph.png
February 03, 2010, at 02:32 AM by 76.22.123.157 -
Changed lines 30-31 from:
> > screen shot of graph
to:
%center% https://www.seedcode.com/rootimages/stikipad/calnext/graph.png
February 03, 2010, at 02:25 AM by 76.22.123.157 -
Changed lines 44-45 from:
-> On your relationship graph, link "CalendarRows" to "CalendarInterface" to "SampleEvents" as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file. Where you see "id" in our SampleEvents table, use the unique primary key from your events table. Link the Sample Events table to a new instance of your contact's table if you'd like.
to:
-> On your relationship graph, link "CalendarRows" to "CalendarInterface" as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file.
February 02, 2010, at 03:16 PM by 76.22.123.157 -
Changed lines 77-78 from:
-> Trigger: OnRecordLoad - "Load Calendar Layout"
-> Trigger: OnLayoutLoad - "Load Calendar Layout"
to:
-> Trigger: OnRecordLoad - "Load Calendar Layout" (in Browse and Find Mode)
January 19, 2010, at 05:08 AM by 76.22.123.157 -
Changed line 76 from:
-> Layout: Calendar (2 trigger2)
to:
-> Layout: Calendar (2 triggers)
Changed lines 79-81 from:
-> (Do this on each of the two calendar layouts.)

-> Layout: Event Details (2 triggers)
to:
-> (Do this on each of the four calendar layouts.)

-> Layout: Event Details (1 trigger)
Changed lines 83-84 from:
-> Trigger: OnRecordCommit - "Close Window & Refresh Calendar" (we're no longer doing this one as a script trigger. it was pretty annoying).
to:
January 19, 2010, at 05:06 AM by 76.22.123.157 -
Changed lines 70-71 from:
-> When you get to Event Details feel free to edit this layout as you see fit, adding your own fields and buttons. Just be sure to keep the following 3 objects: the "repeat" button, the "show repts..." button below it, ad the large "close..." button at the bottom of the screen.
to:
-> When you get to Event Details feel free to edit this layout as you see fit, adding your own fields and buttons. Just be sure to keep the following 3 objects: the "repeat" button, the "show repts..." button below it, and the large "close..." button at the bottom of the screen.
January 05, 2010, at 11:02 PM by 76.22.123.157 -
Changed lines 77-78 from:
-> Trigger: OnRecordLoad - "Load Calendar Layout from tab script triggers"
-> Trigger: OnLayoutLoad - "Load Calendar Layout from tab script triggers
"
to:
-> Trigger: OnRecordLoad - "Load Calendar Layout"
-> Trigger: OnLayoutLoad -
"Load Calendar Layout"
December 30, 2009, at 01:12 AM by 76.22.123.157 -
Added lines 36-37:
-> Here, and in what follows, you don't need to import anything to do with SampleContacts as you'll likely already have these things in your file.
Changed lines 44-45 from:
-> On your relationship graph, link "CalendarRows" to "CalendarInterface" to "SampleEvents" as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file. Where you see "id" in our SampleEvents table, use the unique primary key from your events table.
to:
-> On your relationship graph, link "CalendarRows" to "CalendarInterface" to "SampleEvents" as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file. Where you see "id" in our SampleEvents table, use the unique primary key from your events table. Link the Sample Events table to a new instance of your contact's table if you'd like.
Changed lines 52-53 from:
-> Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them.
to:
-> Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Again, you don't need to import the contact layouts unless you don't have any of your own.
December 30, 2009, at 01:10 AM by 76.22.123.157 -
Changed lines 28-29 from:
-> Import two tables into you file from SeedCode Calendar: Calendar Rows and Calendar Interface. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us your file.
to:
-> Import two tables into your file from SeedCode Calendar: Calendar Rows and Calendar Interface. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us your file.
December 30, 2009, at 12:32 AM by 76.22.123.157 -
Changed lines 87-90 from:
-> '''11.2 Sort your records.''' Edit the script "Sort FileMaker Records..." and follow the instructions to sort your records by date / time ascending, editing the sort step there to use fields from your events table.

->
'''11.3 Map your data.''' Then go to the layout "Source No 1" and follow the directions on the layout to map the fields there to the fields in your SampleEvents table.
to:
-> '''11.2 Sort your records.''' Edit the script "Sort FileMaker Records..." and follow the instructions to sort your records by date / time ascending, editing the sort step there to use fields from your events table.

->
'''11.3 Map your data.''' Then go to the layout "Source No 1" and follow the directions on the layout to map the fields there to the fields in your SampleEvents table. Map the "Summary" to a simple field for now like your event's title, just to get you up and running, then return here and try mapping the summary to something more interesting to create a [[MultiLineEvents | multi-line event]] display.
December 29, 2009, at 07:24 PM by 76.22.123.157 -
Added lines 58-59:
-> Now you may already have layouts you want to use for your Event List and Event Details. If so, take a moment to read about that here: using [[your own Event layouts]].
December 28, 2009, at 08:29 PM by 76.22.123.157 -
Changed lines 85-86 from:
-> '''11.2 Sort your records.'' Edit the script "Sort FileMaker Records..." and follow the instructions to sort your records by date / time ascending, editing the sort step there to use fields from your events table.
to:
-> '''11.2 Sort your records.''' Edit the script "Sort FileMaker Records..." and follow the instructions to sort your records by date / time ascending, editing the sort step there to use fields from your events table.
December 28, 2009, at 08:28 PM by 76.22.123.157 -
Changed lines 3-4 from:
Most folks will paste SeedCode Calendar into their file and use an events table they already have for the events they want to see in the calendar. These instructions are for them. If you want to use the Sample Events table in SeedCode Calendar as your events table, just import it into your file in step 2 below and skip step 4.
to:
Most folks will paste SeedCode Calendar into their file and use an events table they already have for the events they want to see in the calendar. These instructions are for them. If you want to use the Sample Events table in SeedCode Calendar as your events table, just import it into your file in step 2 below and skip step 5.
December 28, 2009, at 08:06 PM by 76.22.123.157 -
Changed lines 7-8 from:
-> Really. And while you're at it, review a [[YourFile | couple of things]] you may want to change in your file before you get started.
to:
-> Really.

->
And this is '''important''': review a [[YourFile | couple of things]] you may want to change in your file before you get started.
December 24, 2009, at 06:32 PM by 76.22.123.157 -
Changed lines 81-84 from:
-> '''11.1 Configure the calendar.''' Edit the script "Load Calendar Settings - On Startup" and follow the comments changing values as necessary.

-> '''11.2 Map your data.''' Then go to the layout "Source No 1" and follow the directions on the layout to map the fields there to the fields in your SampleEvents table.
to:
-> '''11.1 Configure the calendar.''' Edit the script "Load Calendar Settings - On Startup..." and follow the comments changing values as necessary.

-> '''11.2 Sort your records.'' Edit the script "Sort FileMaker Records..." and follow the instructions to sort your records by date / time ascending, editing the sort step there to use fields from your events table.

-> '''11.3
Map your data.''' Then go to the layout "Source No 1" and follow the directions on the layout to map the fields there to the fields in your SampleEvents table.
December 22, 2009, at 07:49 AM by 76.22.123.157 -
Changed lines 7-8 from:
-> Really.
to:
-> Really. And while you're at it, review a [[YourFile | couple of things]] you may want to change in your file before you get started.
December 20, 2009, at 07:15 PM by 76.22.123.157 -
Changed lines 81-82 from:
-> Configure the calendar. Edit the script "Load Calendar Settings - On Startup" and follow the comments changing values as necessary. The go to the layout "Source No 1" and follow the directions on the layout to map the fields there to the fields in your Sample Events table.
to:
-> '''11.1 Configure the calendar.''' Edit the script "Load Calendar Settings - On Startup" and follow the comments changing values as necessary.

-> '''11.2 Map your data.''' Then go to the layout "Source No 1" and follow the directions on
the layout to map the fields there to the fields in your SampleEvents table.
December 20, 2009, at 07:13 PM by 76.22.123.157 -
December 20, 2009, at 07:13 PM by 76.22.123.157 -
Added lines 64-65:
-> When you get to Event Details feel free to edit this layout as you see fit, adding your own fields and buttons. Just be sure to keep the following 3 objects: the "repeat" button, the "show repts..." button below it, ad the large "close..." button at the bottom of the screen.
December 20, 2009, at 07:09 PM by 76.22.123.157 -
Changed lines 68-69 from:
-> Layout: Calendar (1 trigger)
-> Trigger: OnRecordLoad - "Load Calendar Layout (tabbed)"
to:
-> Layout: Calendar (2 trigger2)
-> Trigger: OnRecordLoad - "Load Calendar Layout from tab script triggers"
-> Trigger: OnLayoutLoad - "Load Calendar Layout from tab script triggers
"
December 20, 2009, at 07:07 PM by 76.22.123.157 -
Changed lines 70-71 from:
to:
-> (Do this on each of the two calendar layouts.)
December 20, 2009, at 06:54 PM by 76.22.123.157 -
Changed lines 62-63 from:
-> Now copy the layout contents from each layout in SeedCode Calendar and paste them into the layout of the same name in your file. And yes, we do need the contents of "Calendar Records" on that layout. The contents of "Developer" are optional.
to:
-> Now copy the layout contents from each layout in SeedCode Calendar and paste them into the layout of the same name in your file. And yes, we do need the contents of "Calendar Records" on that layout. The contents of "Developer" are optional. You'll be warned that you'll be increasing the size of each layout; that's OK.
December 20, 2009, at 06:48 PM by 76.22.123.157 -
December 20, 2009, at 06:48 PM by 76.22.123.157 -
Changed lines 58-59 from:
-> Import the scripts from SeedCode Calendar. When importing, just click the check box beside the folder "SeedCode Calendar" and all the scripts within that folder will import.
to:
-> Import the scripts from SeedCode Calendar. When importing, just click the check box beside the folder "SeedCode Calendar" and all the scripts within that folder will import. There will be a number of errors reports when you import: this is normal. In "Setup" below we'll remap some of the fields and settings in these scripts to values in your file.
December 20, 2009, at 06:42 PM by 76.22.123.157 -
Changed lines 48-49 from:
-> Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Delete the default layouts created when you imported tables in step 3.
to:
-> Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. 

-> You may want to create the separator layouts we have as well (these are based on Calendar Events) but that is just cosmetic.

->
Delete the default layouts created when you imported tables in step 3.
December 20, 2009, at 06:34 PM by 76.22.123.157 -
December 20, 2009, at 06:34 PM by 76.22.123.157 -
Changed lines 38-39 from:
'''6. One Relationship.'''
to:
'''6. Relationships.'''
December 20, 2009, at 06:32 PM by 76.22.123.157 -
Changed lines 40-41 from:
-> On your relationship graph, link "CalendarRows" to "CalendarInterface" to "SampleEvents" as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file. At this point, if you want to show event colors in list view as we do in the Event List or Event Detail layouts, copy our field "z_ColorCalc" from Sample Events and add it to your events table. Where you see "id" in our SampleEvents table, use the unique primary key from your events table.
to:
-> On your relationship graph, link "CalendarRows" to "CalendarInterface" to "SampleEvents" as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file. Where you see "id" in our SampleEvents table, use the unique primary key from your events table.

-> At this point, if you want to show event colors in list view as we do in the Event List or Event Detail layouts, copy
our field "z_ColorCalc" from Sample Events and add it to your events table mapping our field "status" to the equivalent field in your table: this is the field we used to color code events in the calendar.
December 20, 2009, at 05:52 PM by 76.22.123.157 -
December 20, 2009, at 05:52 PM by 76.22.123.157 -
Changed lines 40-41 from:
-> On your relationship graph, link "CalendarRows" to "CalendarInterface" to "SampleEvents" as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file. At this point, if you want to show event colors in list view as we do in the Event List or Event Detail layouts, copy our field "z_ColorCalc" from Sample Events and add it to your events table.
to:
-> On your relationship graph, link "CalendarRows" to "CalendarInterface" to "SampleEvents" as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file. At this point, if you want to show event colors in list view as we do in the Event List or Event Detail layouts, copy our field "z_ColorCalc" from Sample Events and add it to your events table. Where you see "id" in our SampleEvents table, use the unique primary key from your events table.
December 20, 2009, at 05:47 PM by 76.22.123.157 -
Changed lines 40-41 from:
-> On your relationship graph, link "CalendarRows" to "CalendarInterface" to "SampleEvents" as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file. At this point, if you want to show event colors in list view as we do in the Event List layout, copy our field "z_ColorCalc" from Sample Events and add it to your events table.
to:
-> On your relationship graph, link "CalendarRows" to "CalendarInterface" to "SampleEvents" as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file. At this point, if you want to show event colors in list view as we do in the Event List or Event Detail layouts, copy our field "z_ColorCalc" from Sample Events and add it to your events table.
December 20, 2009, at 05:47 PM by 76.22.123.157 -
Changed lines 40-41 from:
-> Relate Calendar Rows to Calendar Interface to Sample Events as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file. At this point, if you want to show event colors in list view as we do in the Event List layout, copy our field "z_ColorCalc" from Sample Events and add it to your events table.
to:
-> On your relationship graph, link "CalendarRows" to "CalendarInterface" to "SampleEvents" as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file. At this point, if you want to show event colors in list view as we do in the Event List layout, copy our field "z_ColorCalc" from Sample Events and add it to your events table.
December 20, 2009, at 05:45 PM by 76.22.123.157 -
Deleted lines 17-18:
-> What about the color field: we should probably add that as well.
Changed lines 36-37 from:
-> Create a new occurrence of your events table (the table that has the records you want to see on the calendar) and name it "Sample Events". You can change this name later.
to:
-> Create a new occurrence of your events table (the table that has the records you want to see on the calendar) and name it "SampleEvents" (make sure there are no spaces in the table occurrence name). You can change this name later.
December 20, 2009, at 05:39 PM by 76.22.123.157 -
Changed lines 34-35 from:
-> Open SeedCode Calendar and recreate the 5 value lists in your file. Feel free to use your list of statuses and resources. The other values lists need to stay as they are.
to:
-> Open SeedCode Calendar and recreate the 5 value lists in your file. Feel free to use your list of statuses and resources. The other values lists need to stay as they are, though you can feel free to change the time formats in "Calendar Times" to suit your tastes. You might want to do that later though, once you have this up and running.
December 20, 2009, at 05:30 PM by 76.22.123.157 -
Changed lines 28-29 from:
-> Import two tables into you file from SeedCode Calendar: Calendar Rows and Calendar Interface. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us you file.
to:
-> Import two tables into you file from SeedCode Calendar: Calendar Rows and Calendar Interface. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us your file.
December 20, 2009, at 05:27 PM by 76.22.123.157 -
Changed lines 16-17 from:
-> Replace the DateStart, TimeStart, etc. fields in these calculations with the relevant fields from your events table. Make sure both calcs return the form "timestamp" and that both are indexed.
to:
-> Edit the definitions for these calcs, removing any leading / trailing comment tags if you pasted the fields in using FielMaker Advanced (that is, remove the /* and */ from the beginning and end of the calc. Then replace the DateStart, TimeStart, etc. fields in these calculations with the relevant fields from your events table. Make sure both calcs return the form "timestamp" and that both are indexed.
December 20, 2009, at 05:25 PM by 76.22.123.157 -
Changed lines 11-12 from:
-> 2.1 Add two new fields to your event's table from SeedCode Calendar's Sample Events table:
to:
-> '''2.1''' Add two new fields to your event's table from SeedCode Calendar's Sample Events table:
Changed lines 18-19 from:
-> 2.2 Next, add the following Auto-Enter Calculated Value option to the TimeStart field in your events table:
to:
-> What about the color field: we should probably add that as well.

-> '''2.2'''
Next, add the following Auto-Enter Calculated Value option to the TimeStart field in your events table:
December 20, 2009, at 12:15 AM by 76.22.123.157 -
Changed lines 67-68 from:
-> Trigger: OnRecordCommit - "Refresh Calendar on Comit - mini window version" (we're no longer doing this one as a script trigger. it was pretty annoying).
to:
-> Trigger: OnRecordCommit - "Close Window & Refresh Calendar" (we're no longer doing this one as a script trigger. it was pretty annoying).
December 19, 2009, at 09:36 PM by 76.22.123.157 -
Changed lines 67-68 from:
-> Trigger: OnRecordCommit - "Refresh Calendar on Comit - new window version"
to:
-> Trigger: OnRecordCommit - "Refresh Calendar on Comit - mini window version" (we're no longer doing this one as a script trigger. it was pretty annoying).
November 27, 2009, at 10:01 PM by 76.22.123.157 -
Changed lines 11-12 from:
-> Add two new fields to your event's table from SeedCode Calendar's Sample Events table:
to:
-> 2.1 Add two new fields to your event's table from SeedCode Calendar's Sample Events table:
Changed lines 18-23 from:
to:
-> 2.2 Next, add the following Auto-Enter Calculated Value option to the TimeStart field in your events table:

--> If ( Self = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ; Self )

-> Make sure you uncheck the "Do not replace existing value" checkbox. This Auto-Enter option is needed if you want events to be able to start at midnight.

November 27, 2009, at 09:45 PM by 76.22.123.157 -
Changed lines 9-10 from:
'''2. Tables.'''
to:
'''2. Fields.'''

-> Add two new fields to your event's table from SeedCode Calendar's Sample Events table:

--> z_sc_TimestampEndCalc
--> z_sc_TimestampStartCalc

-> Replace the DateStart, TimeStart, etc. fields in these calculations with the relevant fields from your events table. Make sure both calcs return the form "timestamp" and that both are indexed.


'''3
. Tables.'''
Changed lines 25-26 from:
'''3. Value Lists.'''
to:
'''4. Value Lists.'''
Changed lines 29-30 from:
'''4. Table Occurrences.'''
to:
'''5. Table Occurrences.'''
Changed lines 33-34 from:
'''5. One Relationship.'''
to:
'''6. One Relationship.'''
Changed lines 39-42 from:
'''6. Layouts Part 1.'''

-> Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Delete the default layouts created when you imported tables in step 2.
to:
'''7. Layouts Part 1.'''

-> Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Delete the default layouts created when you imported tables in step 3.
Changed lines 45-46 from:
'''7. Scripts.'''
to:
'''8. Scripts.'''
Changed lines 49-50 from:
'''8. Layouts Part 2.'''
to:
'''9. Layouts Part 2.'''
Changed lines 53-54 from:
'''9. Layout Script Triggers.'''
to:
'''10. Layout Script Triggers.'''
Changed lines 64-65 from:
'''10. Setup.'''
to:
'''11. Setup.'''
Changed lines 68-69 from:
'''11. Clean Up.'''
to:
'''12. Clean Up.'''
Changed lines 72-73 from:
'''12. Run a Script.'''
to:
'''13. Run a Script.'''
November 20, 2009, at 03:32 AM by 76.22.123.157 -
Changed lines 25-26 from:
-> Relate Calendar Rows to Calendar Interface to Sample Events as show on the graph in SeedCode Calendar. Double check that the table occurrence names
to:
-> Relate Calendar Rows to Calendar Interface to Sample Events as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file. At this point, if you want to show event colors in list view as we do in the Event List layout, copy our field "z_ColorCalc" from Sample Events and add it to your events table.
November 19, 2009, at 11:45 PM by 76.22.123.157 -
November 19, 2009, at 11:42 PM by 76.22.123.157 -
Changed lines 5-8 from:
'''1. Backup your file.''' Really.

'''2. Tables.''' Import two tables into you file from SeedCode Calendar: Calendar Rows and Calendar Interface. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us you file.
to:
'''1. Backup your file.'''

->
Really.

'''2. Tables.''' 

->
Import two tables into you file from SeedCode Calendar: Calendar Rows and Calendar Interface. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us you file.
Changed lines 15-20 from:
'''3. Value Lists.''' Open SeedCode Calendar and recreate the 5 value lists in your file. Feel free to use your list of statuses and resources. The other values lists need to stay as they are.

'''4. Table Occurrences.''' Create a new occurrence of your events table (the table that has the records you want to see on the calendar) and name it "Sample Events". You can change this name later.

'''5. One Relationship''' Relate Calendar Rows to Calendar Interface to Sample Events as show on the graph in SeedCode Calendar. Double check that the table occurrence names
to:
'''3. Value Lists.'''

->
Open SeedCode Calendar and recreate the 5 value lists in your file. Feel free to use your list of statuses and resources. The other values lists need to stay as they are.

'''4. Table Occurrences.'''

->
Create a new occurrence of your events table (the table that has the records you want to see on the calendar) and name it "Sample Events". You can change this name later.

'''5. One Relationship.''' 

->
Relate Calendar Rows to Calendar Interface to Sample Events as show on the graph in SeedCode Calendar. Double check that the table occurrence names
Changed lines 29-30 from:
'''6. Layouts Part 1.''' Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Delete the default layouts created when you imported tables in step 2.
to:
'''6. Layouts Part 1.''' 

->
Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Delete the default layouts created when you imported tables in step 2.
Changed lines 35-40 from:
'''7. Scripts.''' Import the scripts from SeedCode Calendar. When importing, just click the check box beside the folder "SeedCode Calendar" and all the scripts within that folder will import.

'''8. Layouts Part 2.''' Now copy the layout contents from each layout in SeedCode Calendar and paste them into the layout of the same name in your file. And yes, we do need the contents of "Calendar Records" on that layout. The contents of "Developer" are optional.

'''9. Layout Script Triggers.''' Assign script triggers. Since layout level script triggers don't come over when you copy and paste layout elements, you'll have to recreate these. Fortunately there are only a few.
to:
'''7. Scripts.'''

->
Import the scripts from SeedCode Calendar. When importing, just click the check box beside the folder "SeedCode Calendar" and all the scripts within that folder will import.

'''8. Layouts Part 2.'''

->
Now copy the layout contents from each layout in SeedCode Calendar and paste them into the layout of the same name in your file. And yes, we do need the contents of "Calendar Records" on that layout. The contents of "Developer" are optional.

'''9. Layout Script Triggers.''' 

->
Assign script triggers. Since layout level script triggers don't come over when you copy and paste layout elements, you'll have to recreate these. Fortunately there are only a few.
Changed lines 54-59 from:
'''10. Setup.''' Configure the calendar. Edit the script "Load Calendar Settings - On Startup" and follow the comments changing values as necessary. The go to the layout "Source No 1" and follow the directions on the layout to map the fields there to the fields in your Sample Events table.

'''11. Clean Up.''' Rename your Sample Events table occurrence to something that makes more sense for you. And add the script "Upon Opening" to your file's opening script, removing the go to layout stuff if you'd like.

'''12. Run a Script.''' That's it. Run the script "Upon Opening" script and you should see your events in the day view.
to:
'''10. Setup.'''

->
Configure the calendar. Edit the script "Load Calendar Settings - On Startup" and follow the comments changing values as necessary. The go to the layout "Source No 1" and follow the directions on the layout to map the fields there to the fields in your Sample Events table.

'''11. Clean Up.'''

->
Rename your Sample Events table occurrence to something that makes more sense for you. And add the script "Upon Opening" to your file's opening script, removing the go to layout stuff if you'd like.

'''12. Run a Script.''' 

->
That's it. Run the script "Upon Opening" script and you should see your events in the day view.
November 19, 2009, at 11:41 PM by 76.22.123.157 -
Changed lines 5-8 from:
'''1.''' Backup your file. Really.

'''2.''' Import two tables into you file from SeedCode Calendar: Calendar Rows and Calendar Interface. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us you file.
to:
'''1. Backup your file.''' Really.

'''2. Tables
.''' Import two tables into you file from SeedCode Calendar: Calendar Rows and Calendar Interface. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us you file.
Changed lines 11-16 from:
'''3.''' Open SeedCode Calendar and recreate the 5 value lists in your file. Feel free to use your list of statuses and resources. The other values lists need to stay as they are.

'''4.''' Create a new occurrence of your events table (the table that has the records you want to see on the calendar) and name it "Sample Events". You can change this name later.

'''5.''' Relate Calendar Rows to Calendar Interface to Sample Events as show on the graph in SeedCode Calendar. Double check that the table occurrence names
to:
'''3. Value Lists.''' Open SeedCode Calendar and recreate the 5 value lists in your file. Feel free to use your list of statuses and resources. The other values lists need to stay as they are.

'''4. Table Occurrences.''' Create a new occurrence of your events table (the table that has the records you want to see on the calendar) and name it "Sample Events". You can change this name later.

'''5. One Relationship''' Relate Calendar Rows to Calendar Interface to Sample Events as show on the graph in SeedCode Calendar. Double check that the table occurrence names
Changed lines 19-20 from:
'''6.''' Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Delete the default layouts created when you imported tables in step 2.
to:
'''6. Layouts Part 1.''' Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Delete the default layouts created when you imported tables in step 2.
Changed lines 23-28 from:
'''7.''' Import the scripts from SeedCode Calendar. When importing, just click the check box beside the folder "SeedCode Calendar" and all the scripts within that folder will import.

'''8.''' Now copy the layout contents from each layout in SeedCode Calendar and paste them into the layout of the same name in your file. And yes, we do need the contents of "Calendar Records" on that layout. The contents of "Developer" are optional.

'''9.''' Assign script triggers. Since layout level script triggers don't come over when you copy and paste layout elements, you'll have to recreate these. Fortunately there are only a few.
to:
'''7. Scripts.''' Import the scripts from SeedCode Calendar. When importing, just click the check box beside the folder "SeedCode Calendar" and all the scripts within that folder will import.

'''8. Layouts Part 2.''' Now copy the layout contents from each layout in SeedCode Calendar and paste them into the layout of the same name in your file. And yes, we do need the contents of "Calendar Records" on that layout. The contents of "Developer" are optional.

'''9. Layout Script Triggers.''' Assign script triggers. Since layout level script triggers don't come over when you copy and paste layout elements, you'll have to recreate these. Fortunately there are only a few.
Changed lines 36-41 from:
'''10.''' Configure the calendar. Edit the script "Load Calendar Settings - On Startup" and follow the comments changing values as necessary. The go to the layout "Source No 1" and follow the directions on the layout to map the fields there to the fields in your Sample Events table.

'''11.''' Rename your Sample Events table occurrence to something that makes more sense for you. And add the script "Upon Opening" to your file's opening script, removing the go to layout stuff if you'd like.

'''12.''' That's it. Run the script "Upon Opening" script and you should see your events in the day view.
to:
'''10. Setup.''' Configure the calendar. Edit the script "Load Calendar Settings - On Startup" and follow the comments changing values as necessary. The go to the layout "Source No 1" and follow the directions on the layout to map the fields there to the fields in your Sample Events table.

'''11. Clean Up.''' Rename your Sample Events table occurrence to something that makes more sense for you. And add the script "Upon Opening" to your file's opening script, removing the go to layout stuff if you'd like.

'''12. Run a Script.''' That's it. Run the script "Upon Opening" script and you should see your events in the day view.
November 19, 2009, at 05:26 PM by 76.22.123.157 -
Changed lines 25-26 from:
'''8.''' Now copy the layout contents from each layout in SeedCode Calendar and paste them into the layout of the same name in your file.
to:
'''8.''' Now copy the layout contents from each layout in SeedCode Calendar and paste them into the layout of the same name in your file. And yes, we do need the contents of "Calendar Records" on that layout. The contents of "Developer" are optional.
Changed lines 29-35 from:
-> Layout: Calendar
-> Trigger(s): OnRecordLoad - "Load Calendar Layout (tabbed)"

-> Layout: Event Details
-> Trigger(s): OnRecordLoad - "On Event Record Load"
-> Trigger(s): OnRecordCommit - "Refresh Calendar on Comit - new window version"
to:
-> Layout: Calendar (1 trigger)
-> Trigger: OnRecordLoad - "Load Calendar Layout (tabbed)"

-> Layout: Event Details (2 triggers)
-> Trigger: OnRecordLoad - "On Event Record Load"
-> Trigger: OnRecordCommit - "Refresh Calendar on Comit - new window version"
Changed lines 40-41 from:
'''12.''' That's it. Run the script "Upon Opening" script and you should see your events in the month view.
to:
'''12.''' That's it. Run the script "Upon Opening" script and you should see your events in the day view.
November 16, 2009, at 04:14 PM by 76.22.123.157 -
Changed lines 34-35 from:
                  OnRecordCommit - "Refresh Calendar on Comit - new window version"
to:
-> Trigger(s): OnRecordCommit - "Refresh Calendar on Comit - new window version"
November 16, 2009, at 05:11 AM by 76.22.123.157 -
Changed lines 5-8 from:
1. Backup your file. Really.

2. Import two tables into you file from SeedCode Calendar: Calendar Rows and Calendar Interface. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us you file.
to:
'''1.''' Backup your file. Really.

'''2.''' Import two tables into you file from SeedCode Calendar: Calendar Rows and Calendar Interface. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us you file.
Changed lines 11-16 from:
3. Open SeedCode Calendar and recreate the 5 value lists in your file. Feel free to use your list of statuses and resources. The other values lists need to stay as they are.

4. Create a new occurrence of your events table (the table that has the records you want to see on the calendar) and name it "Sample Events". You can change this name later.

5. Relate Calendar Rows to Calendar Interface to Sample Events as show on the graph in SeedCode Calendar. Double check that the table occurrence names
to:
'''3.''' Open SeedCode Calendar and recreate the 5 value lists in your file. Feel free to use your list of statuses and resources. The other values lists need to stay as they are.

'''4.''' Create a new occurrence of your events table (the table that has the records you want to see on the calendar) and name it "Sample Events". You can change this name later.

'''5.''' Relate Calendar Rows to Calendar Interface to Sample Events as show on the graph in SeedCode Calendar. Double check that the table occurrence names
Changed lines 19-20 from:
6. Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Delete the default layouts created when you imported tables in step 2.
to:
'''6.''' Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Delete the default layouts created when you imported tables in step 2.
Changed lines 23-28 from:
7. Import the scripts from SeedCode Calendar. When importing, just click the check box beside the folder "SeedCode Calendar" and all the scripts within that folder will import.

8. Now copy the layout contents from each layout in SeedCode Calendar and paste them into the layout of the same name in your file.

9. Assign script triggers. Since layout level script triggers don't come over when you copy and paste layout elements, you'll have to recreate these. Fortunately there are only a few.
to:
'''7.''' Import the scripts from SeedCode Calendar. When importing, just click the check box beside the folder "SeedCode Calendar" and all the scripts within that folder will import.

'''8.''' Now copy the layout contents from each layout in SeedCode Calendar and paste them into the layout of the same name in your file.

'''9.''' Assign script triggers. Since layout level script triggers don't come over when you copy and paste layout elements, you'll have to recreate these. Fortunately there are only a few.
Changed lines 36-41 from:
10. Configure the calendar. Edit the script "Load Calendar Settings - On Startup" and follow the comments changing values as necessary. The go to the layout "Source No 1" and follow the directions on the layout to map the fields there to the fields in your Sample Events table.

11. Rename your Sample Events table occurrence to something that makes more sense for you. And add the script "Upon Opening" to your file's opening script, removing the go to layout stuff if you'd like.

12. That's it. Run the script "Upon Opening" script and you should see your events in the month view.
to:
'''10.''' Configure the calendar. Edit the script "Load Calendar Settings - On Startup" and follow the comments changing values as necessary. The go to the layout "Source No 1" and follow the directions on the layout to map the fields there to the fields in your Sample Events table.

'''11.''' Rename your Sample Events table occurrence to something that makes more sense for you. And add the script "Upon Opening" to your file's opening script, removing the go to layout stuff if you'd like.

'''12.''' That's it. Run the script "Upon Opening" script and you should see your events in the month view.
November 16, 2009, at 05:10 AM by 76.22.123.157 - `
Added lines 15-16:
5. Relate Calendar Rows to Calendar Interface to Sample Events as show on the graph in SeedCode Calendar. Double check that the table occurrence names
Changed lines 19-20 from:
5. Create a few layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events.
to:
6. Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Delete the default layouts created when you imported tables in step 2.
Changed lines 23-42 from:
6.
to:
7. Import the scripts from SeedCode Calendar. When importing, just click the check box beside the folder "SeedCode Calendar" and all the scripts within that folder will import.

8. Now copy the layout contents from each layout in SeedCode Calendar and paste them into the layout of the same name in your file.

9. Assign script triggers. Since layout level script triggers don't come over when you copy and paste layout elements, you'll have to recreate these. Fortunately there are only a few.

-> Layout: Calendar
-> Trigger(s): OnRecordLoad - "Load Calendar Layout (tabbed)"

-> Layout: Event Details
-> Trigger(s): OnRecordLoad - "On Event Record Load"
                    OnRecordCommit - "Refresh Calendar on Comit - new window version"

10. Configure the calendar. Edit the script "Load Calendar Settings - On Startup" and follow the comments changing values as necessary. The go to the layout "Source No 1" and follow the directions on the layout to map the fields there to the fields in your Sample Events table.

11. Rename your Sample Events table occurrence to something that makes more sense for you. And add the script "Upon Opening" to your file's opening script, removing the go to layout stuff if you'd like.

12. That's it. Run the script "Upon Opening" script and you should see your events in the month view.

Enjoy!
November 16, 2009, at 04:56 AM by 76.22.123.157 - `
Added lines 1-21:
!! Adding SeedCode Calendar to your File: the Quick Version.

Most folks will paste SeedCode Calendar into their file and use an events table they already have for the events they want to see in the calendar. These instructions are for them. If you want to use the Sample Events table in SeedCode Calendar as your events table, just import it into your file in step 2 below and skip step 4.

1. Backup your file. Really.

2. Import two tables into you file from SeedCode Calendar: Calendar Rows and Calendar Interface. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us you file.

> > screen shot of graph

3. Open SeedCode Calendar and recreate the 5 value lists in your file. Feel free to use your list of statuses and resources. The other values lists need to stay as they are.

4. Create a new occurrence of your events table (the table that has the records you want to see on the calendar) and name it "Sample Events". You can change this name later.

> > screen shot of graph

5. Create a few layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events.

> > screen shot of layout list

6.
(855) SEEDCODE
support@seedcode.com
Follow us: