DayBackForFileMaker

Your File

DayBackForFileMaker.YourFile History

Hide minor edits - Show changes to output

Changed line 13 from:
%color=red% >> List of layouts to be pasted in
to:
%center% https://www.seedcode.com/rootimages/stikipad/dayback/dayback-layouts.png
Changed lines 1-2 from:
!! Do I need to do anything special to get my file ready for SeedCode Calendar?
to:
!! Do I need to do anything special to get my file ready for DayBack?
Deleted lines 6-7:
'''File Name.''' You can't have a period in your file name (the dot before fp7 in the file name is fine, but something like MyCompany.com.fp7 is not).
Changed lines 11-33 from:
'''Layout Names.''' FileMaker really can't distinguish between layouts of the same name when importing scripts, so take a look at your solution and rename any of your layouts (at least until your done importing calendar scripts) that have the same names as the layouts you'll be pasting in from SeedCode Calendar:

-
> Calendar Home
-> -\\
Calendar\\
Calendar - no Side Menu\\
-\\
Calendar - Small\\
Calendar - Small - no Side Menu\\
-\\
Event List\\
Event Details\\
Event Details Web\\
Repeat Options\\
Assign Colors\\
-\\
Documentation\\
-\\
Source No 1\\
Source No 2\\
-\\
Calendar Records\\
Calendar Color Records\\
to:
'''Layout Names.''' FileMaker really can't distinguish between layouts of the same name when importing scripts, so take a look at your solution and rename any of your layouts (at least until your done importing calendar scripts) that have the same names as the layouts you'll be pasting in from DayBack.

%color=red%
>> List of layouts to be pasted in
February 25, 2013, at 04:09 AM by 98.245.113.231 -
Changed lines 37-38 from:
'''Layout & Script Folders''' FileMaker also fails distinguish between the names of layout folders and the names of actual layouts. So if you create a layout folder named "calendar", many of our navigation routines will fail as FileMaker tries to go to the "calendar" layout which would actually be a layout folder. Scripts aren't as bad but script folders can cause imported scripts to be renamed if they share the same name.
to:
'''Layout & Script Folders''' FileMaker also fails to distinguish between the names of layout folders and the names of actual layouts. So if you create a layout folder named "calendar", many of our navigation routines will fail as FileMaker tries to go to the "calendar" layout which would actually be a layout folder. Scripts aren't as bad but script folders can cause imported scripts to be renamed if they share the same name.
May 03, 2010, at 09:29 PM by 67.171.26.249 -
Added lines 36-39:

'''Layout & Script Folders''' FileMaker also fails distinguish between the names of layout folders and the names of actual layouts. So if you create a layout folder named "calendar", many of our navigation routines will fail as FileMaker tries to go to the "calendar" layout which would actually be a layout folder. Scripts aren't as bad but script folders can cause imported scripts to be renamed if they share the same name.

So, don't make any generic layout or script folder names that might conflict with names already in use in the calendar. If you want to put all the calendar layouts in a folder, call the folder "Calendar Layouts" instead of "Calendar".
February 24, 2010, at 11:31 PM by 76.22.123.157 -
Changed lines 7-8 from:
'''File Name.''' You can't have a period in your file name (the dot before fp7 in the file name is fine, but something like MyComany.com.fp7 is not).
to:
'''File Name.''' You can't have a period in your file name (the dot before fp7 in the file name is fine, but something like MyCompany.com.fp7 is not).
February 03, 2010, at 06:01 PM by 76.22.123.157 -
Changed lines 15-16 from:
--> Calendar Home
--> -\\
to:
-> Calendar Home
-> -\\
February 03, 2010, at 06:01 PM by 76.22.123.157 -
Changed lines 7-10 from:
-> '''File Name.''' You can't have a period in your file name (the dot before fp7 in the file name is fine, but something like MyComany.com.fp7 is not).

-> '''Privilege Sets.''' If you've done a lot of work customizing the privilege sets in your file, you may have "any new table" set to be pretty restrictive. You'll be adding to new tables when you integrate the calendar and you users will need to be able to add, edit, and delete records in both (these are just interface tables-- there is no data there). So if you think this applies to you, then you already know what to do after you create the new tables.
to:
'''File Name.''' You can't have a period in your file name (the dot before fp7 in the file name is fine, but something like MyComany.com.fp7 is not).

'''Privilege Sets.''' If you've done a lot of work customizing the privilege sets in your file, you may have "any new table" set to be pretty restrictive. You'll be adding three new tables when you integrate the calendar and your users will need to be able to add, edit, and delete records in all three (these are just interface tables-- there is no data there). So if you think this applies to you, then you already know what to do after you create the new tables.
Changed lines 13-14 from:
-> '''Layout Names.''' FileMaker really can't distinguish between layouts of the same name when importing scripts, so take a look at your solution and rename any of your layouts (at least until your done importing calendar scripts) that have the same names as the layouts you'll be pasting in from SeedCode Calendar:
to:
'''Layout Names.''' FileMaker really can't distinguish between layouts of the same name when importing scripts, so take a look at your solution and rename any of your layouts (at least until your done importing calendar scripts) that have the same names as the layouts you'll be pasting in from SeedCode Calendar:
Added line 18:
Calendar - no Side Menu\\
Changed lines 20-21 from:
Calendar - no Side Menu\\
to:
Calendar - Small\\
Calendar - Small
- no Side Menu\\
Added line 27:
Assign Colors\\
Changed lines 34-35 from:
Calendar Records\
to:
Calendar Records\\
Calendar Color Records\
\
December 29, 2009, at 07:18 AM by 76.22.123.157 -
Changed lines 13-14 from:
-> '''Layout Names.''' FileMaker really can't distinguish between layouts of the same name when importing scripts, so take a look at your solution and rename (at least until your done importing calendar scripts) any layouts that have the same names as the layouts you'll be pasting in from SeedCode Calendar:
to:
-> '''Layout Names.''' FileMaker really can't distinguish between layouts of the same name when importing scripts, so take a look at your solution and rename any of your layouts (at least until your done importing calendar scripts) that have the same names as the layouts you'll be pasting in from SeedCode Calendar:
December 29, 2009, at 07:17 AM by 76.22.123.157 -
Changed lines 7-8 from:
-> '''File Name.''' You can't have a period in your file name (the dot before fp7 in the file name is fine).
to:
-> '''File Name.''' You can't have a period in your file name (the dot before fp7 in the file name is fine, but something like MyComany.com.fp7 is not).
December 29, 2009, at 07:16 AM by 76.22.123.157 -
Changed lines 5-6 from:
There are a couple things to keep in mind about your file: things that could stop the calendar from working properly if not addressed.
to:
There are, however, a couple things to keep in mind about your file: things that could stop the calendar from working properly if not addressed.
December 24, 2009, at 08:49 PM by 76.22.123.157 -
Deleted line 21:
Event List 2\\
December 24, 2009, at 08:49 PM by 76.22.123.157 -
Changed lines 7-8 from:
-> '''File Name.''' You can't have a period in your file name (the dot before fp7 in the file name is fine.
to:
-> '''File Name.''' You can't have a period in your file name (the dot before fp7 in the file name is fine).
December 24, 2009, at 06:41 PM by 76.22.123.157 -
Added lines 11-12:
-> You'll also want to make sure that the layouts you create are accessible to each of your privilege sets: check the same thing for value lists and scripts.
December 24, 2009, at 06:40 PM by 76.22.123.157 -
Changed lines 11-12 from:
-> '''Layout Names.''' FileMaker really can't distinguish between layouts of the same name when importing scripts, so take a look at your solution and rename (at least until your done importing calendar scripts) any layouts that have the same names as the layouts you'll be importing from SeedCode Calendar:
to:
-> '''Layout Names.''' FileMaker really can't distinguish between layouts of the same name when importing scripts, so take a look at your solution and rename (at least until your done importing calendar scripts) any layouts that have the same names as the layouts you'll be pasting in from SeedCode Calendar:
December 24, 2009, at 06:40 PM by 76.22.123.157 -
Changed lines 15-30 from:
--> Calendar\\
--> -\\
--> Calendar - no Side Menu\\
--> -\\
--> Event List\\
--> Event List 2\\
--> Event Details\\
--> Event Details Web\\
--> Repeat Options\\
--> -\\
--> Documentation\\
--> -\\
--> Source No 1\\
--> Source No 2\\
--> -\\
-->
Calendar Records\
to:
Calendar\\
-\\
Calendar - no Side Menu\\
-\\
Event List\\
Event List 2
\\
Event Details\\
Event Details Web\\
Repeat Options\\
-\\
Documentation\\
-\\
Source No 1
\\
Source No 2\\
-\\
Calendar Records\
December 24, 2009, at 06:39 PM by 76.22.123.157 -
Changed lines 13-31 from:

->Calendar Home
-\\
Calendar\\
-\\
Calendar - no Side Menu\\
-
Event List
Event List 2
Event Details
Event Details Web
Repeat Options
-
Documentation
-
Source No 1
Source No 2
-
Calendar Records
to:
--> Calendar Home
--> -\\
--> Calendar\\
--> -\\
--> Calendar - no Side Menu\\
-->
-\\
--> Event List\\
--> Event List 2\\
--> Event Details\\
--> Event Details Web\\
--> Repeat Options\\
--> -\\
--> Documentation\\
--> -\\
--> Source No 1\\
--> Source No 2\\
--> -\\
--> Calendar Records\
December 24, 2009, at 06:38 PM by 76.22.123.157 -
Added lines 15-18:
-\\
Calendar\\
-\\
Calendar - no Side Menu\\
Deleted lines 19-22:
Calendar
-
Calendar - no Side Menu
-
December 24, 2009, at 06:37 PM by 76.22.123.157 -
Changed lines 13-14 from:
--> Calendar Home
to:

->Calendar Home
Changed line 31 from:
Calendar Records
to:
Calendar Records
December 24, 2009, at 06:37 PM by 76.22.123.157 -
Changed lines 9-30 from:
-> '''Privilege Sets.''' If you've done a lot of work customizing the privilege sets in your file, you may have "any new table" set to be pretty restrictive. You'll be adding to new tables when you integrate the calendar and you users will need to be able to add, edit, and delete records in both (these are just interface tables-- there is no data there). So if you think this applies to you, then you already know what to do after you create the new tables.
to:
-> '''Privilege Sets.''' If you've done a lot of work customizing the privilege sets in your file, you may have "any new table" set to be pretty restrictive. You'll be adding to new tables when you integrate the calendar and you users will need to be able to add, edit, and delete records in both (these are just interface tables-- there is no data there). So if you think this applies to you, then you already know what to do after you create the new tables.

-> '''Layout Names.''' FileMaker really can't distinguish between layouts of the same name when importing scripts, so take a look at your solution and rename (at least until your done importing calendar scripts) any layouts that have the same names as the layouts you'll be importing from SeedCode Calendar:

--> Calendar Home
-
Calendar
-
Calendar - no Side Menu
-
Event List
Event List 2
Event Details
Event Details Web
Repeat Options
-
Documentation
-
Source No 1
Source No 2
-
Calendar Records
December 22, 2009, at 07:49 AM by 76.22.123.157 -
Changed lines 7-9 from:
-> File Name. You can't have a period in your file name (the dot before fp7 in the file name is fine.

-> Privilege Sets. If you've done a lot of work customizing the privilege sets in your file, you may have "any new table" set to be pretty restrictive. You'll be adding to new tables when you integrate the calendar and you users will need to be able to add, edit, and delete records in both (these are just interface tables-- there is no data there). So if you think this applies to you, then you already know what to do after you create the new tables.
to:
-> '''File Name.''' You can't have a period in your file name (the dot before fp7 in the file name is fine.

-> '''Privilege Sets.''' If you've done a lot of work customizing the privilege sets in your file, you may have "any new table" set to be pretty restrictive. You'll be adding to new tables when you integrate the calendar and you users will need to be able to add, edit, and delete records in both (these are just interface tables-- there is no data there). So if you think this applies to you, then you already know what to do after you create the new tables.
December 22, 2009, at 07:48 AM by 76.22.123.157 -
Added lines 1-9:
!! Do I need to do anything special to get my file ready for SeedCode Calendar?

Not really. You'll be pasting the calendar into your file, and importing a number of scripts, but that is all described in our [[integration]] article.

There are a couple things to keep in mind about your file: things that could stop the calendar from working properly if not addressed.

-> File Name. You can't have a period in your file name (the dot before fp7 in the file name is fine.

-> Privilege Sets. If you've done a lot of work customizing the privilege sets in your file, you may have "any new table" set to be pretty restrictive. You'll be adding to new tables when you integrate the calendar and you users will need to be able to add, edit, and delete records in both (these are just interface tables-- there is no data there). So if you think this applies to you, then you already know what to do after you create the new tables.
(855) SEEDCODE
support@seedcode.com
Follow us: