John, The bug fixes as outlined in the V.1.03 documentation are pasted below my signature.
Carl -- Carl Paulsen New Hampshire Rivers Council 54 Portsmouth Street Concord, NH 03301 603-228-6472 603-228-0423 Fax [EMAIL PROTECTED] ************************* EBASE v1.0.3 BUG FIXES, DECEMBER 1, 2000 INTRODUCTION ============= ebase� v1.0.3 was built to: a) convert the ebase� FileMaker Pro templates to the format used by FileMaker Pro version 5, and b) fix some bugs in ebase� that had been identified over the past year on the ebase� SUPPORT listserver (http://www.ebase.org/lists/lists.htm) If you have already converted your ebase� files to Filemaker Pro 5, and you'd rather not go through the process of exporting all your data to ebase� v1.0.3, we have included this documentation that lists the bug fixes that have been included in ebase� v1.0.3. BUG FIXES ========== 1) SUM::Current Fiscal Year Bug ---------------------------------- Fixed a bug in a field calculation that was causing users to get one result when running "Replace All Find Fields", yet getting different results when running "Replace Current Find Fields". TO ADD THIS FIX TO YOUR VERSION OF EBASE: -------------------------------------------- A) Determine if you have this problem: -Get into ebase using your master password. Once you're on the HOME screen, select: File->Define->Fields. -Double-click on the field named "SUM::Current Fiscal Year". -The "Specify Calculation" dialog box will appear. The correct calculation for this field is as follows: If(Month(gToday)>=setup::Fiscal Year Number and setup::Fiscal Year Number> 1, Year(gToday) + 1, Year(gToday)) B) If the calculation for your field reads differently, you should correct it by: -Copying this calculation: If(Month(gToday)>=setup::Fiscal Year Number and setup::Fiscal Year Number> 1, Year(gToday) + 1, Year(gToday)) -Paste this calculation into the "Specify Calculation" dialog box. -Click the "OK" button. -Click the "Done" button. -You should then select and run the "Replace All Find Fields" script from the Scripts menu, leaving the date blank so that it runs for your entire file. PLEDGE MODULE BUGS ------------------ Fixed a few bugs The "pledges" area which lead to inaccurate reporting, The calculations in three calculated fields are involved. 2) Fixed bug in calculating Last Payment Month in PLEDGES ----------------------------------------------------------- TO ADD THIS FIX TO YOUR VERSION OF EBASE: -------------------------------------------- A) Determine if this is a problem: -Get into ebase using your master password. - Once you're on the HOME screen, Click on the Pledges button and them the View pledges button to bring you to the pledges_.102 file. Now select: File->Define->Fields. -Double-click on the field named "Last Payment Month". -The "Specify Calculation" dialog box will appear. The correct calculation for this field is as follows: Month(Gift::Post Date) B) If the calculation for your field reads differently, you should correct it by: -Copying this calculation: Month(Gift::Post Date) -Paste this calculation into the "Specify Calculation" dialog box. -Click the "OK" button. -Click the "Done" button. 3) Fixed bug in calculating Last Payment Received in PLEDGES --------------------------------------------------------------- TO ADD THIS FIX TO YOUR VERSION OF EBASE: -------------------------------------------- A) Determine if this is a problem: -Get into ebase using your master password. Once you're on the HOME screen, Click on the Pledges button and them the View pledges button to bring you to the pledges_.102 file. Now select: File->Define->Fields. -Double-click on the field named "Last Payment Received". -The "Specify Calculation" dialog box will appear. The correct calculation for this field is as follows: Gift::Post Date B) If the calculation for your field reads differently, you should correct it by: -Copying this calculation: Gift::Post Date -Paste this calculation into the "Specify Calculation" dialog box. -Click the "OK" button. -Click the "Done" button. 4) Fixed bug in calculating Last Payment Year in PLEDGES ---------------------------------------------------------- TO ADD THIS FIX TO YOUR VERSION OF EBASE: -------------------------------------------- A) Determine if this is a problem: -Get into ebase using your master password. Once you're on the HOME screen, Click on the Pledges button and them the View pledges button to bring you to the pledges_.102 file. Now select: File->Define->Fields. -Double-click on the field named "Last Payment Year". -The "Specify Calculation" dialog box will appear. The correct calculation for this field is as follows: Year(Gift::Post Date) B) If the calculation for your field reads differently, you should correct it by: -Copying this calculation: Year(Gift::Post Date) -Paste this calculation into the "Specify Calculation" dialog box. -Click the "OK" button. -Click the "Done" button. 5) Fixed bug in the way Global Date is formatted in PLEDGES ------------------------------------------------------------ TO ADD THIS FIX TO YOUR VERSION OF EBASE: -------------------------------------------- A) Determine if this is a problem: -Get into ebase using your master password. Once you're on the HOME screen, Click on the Pledges button and them the View pledges button to bring you to the pledges_.102 file. Now select: File->Define->Fields. -Double-click on the field named " Global Date". -The "Specify Calculation" dialog box will appear. The correct calculation for this field is as follows: CONSTANT::gToday -And that the Calculation result is field on the Specify Calculation dialog box is set to "Date" B) If the calculation for your field reads differently, you should correct it by: -Copying this calculation: CONSTANT::gToday -Paste this calculation into the "Specify Calculation" dialog box. -If the Calculation result is field is set not set to "Date", choose "Date" from it's pull down option list. -Click the "OK" button. -Click the "Done" button. PROBLEMS WITH SLOWDOWNS IN TRANSISTION FROM PAYMENT HISTORY TO PAYMENT ----------------------------------------------------------------------- 6) Fixed bug causing slowdown in transition from payment history to payment with large data sets TO ADD THIS FIX TO YOUR VERSION OF EBASE: ----------------------------------------- A) You should determine if you have this problem. -Get into ebase using your master password. Once you're on the HOME screen, select: Scripts > Scriptmaker -From the Define Scripts for Names.102 dialog Double click on the Script names "View Payments Script" -In the Script Definition for View Payments dialog the correct fourth line from the top should read: If[not IsValid(All Payments All Names::Record Number)] B) If the script reads differently - Double Click on the fourth line from the top correct it by - Copy this calculation not IsValid(All Payments All Names::Record Number) - Paste the calculation into the "Specify Calculation" dialog box -Click the "OK" button. -Click the "Done" button. PROBLEMS WITH SUBTOALS IN PAYMENT REPORT BY INDIVIDUAL ------------------------------------------------------- 7) Fixed bug in Script for the R_PAYMENT RPT (ind) causing report not to give individual subtotals in the Payment Report by individual TO ADD THIS FIX TO YOUR VERSION OF EBASE: ----------------------------------------- A) You should determine if you have this problem. - Get into ebase using your master password. Once you're on the HOME screen, select: the "View Payments" button - Choose Scripts > Scriptmaker - From the Scriptmaker define scripts dialog: Click on the R_PAYMENT RPT script - Press the Perform button to run the script B) If your report should have both an Individual Total for each individual as well as a Grand Total for the report, if it does not: - From the Scriptmaker define scripts dialog: Click on the R_PAYMENT RPT script - Press the Perform button to run the script - Click the "Continue" button then Click the " No" button to exit from the report - Open the sort dialog. (CTRL-S), Should read: Names::Last Name 1 Names::First Name 1 Names::Business\Organization - Double click on "Record Number" to the bottom of the sort list. Should now read: Names::Last Name 1 Names::First Name 1 Names::Business\Organization Record Number - Click the "Sort" Button - Return to the Scripts > Scriptmaker Define scripts dialog - Double click on the R_PAYMENT RPT script - Click the "OK" Button - On the Information Needed dialog for "Sort Order" choose the "Replace" option - Click the "OK" button You should have stored your new sort order and there should now be an individual Total line as well as a Grand Total line in the report when you run it. BUG IN EXPIRATION OF INDEFINITE MEMBERSHIPS --------------------------------------------- 8) Problem with expiration of indefinite memberships -------------------------------------------------------------------------- Fixed Bug where ebase, under some conditions, erroneously reported the expiration of indefinite memberships as the last expiration date of a past full membership for that member. eBase now figures a changing future date for expiration of indefinite members based on system date. TO ADD THIS FIX TO YOUR VERSION OF EBASE: ----------------------------------------- A) Determine if this is a problem: -Get into ebase using your master password. Once you're on the HOME screen, Click on the Pledges button and them the View pledges button to bring you to the pledges_.102 file. Now select: File->Define->Fields. -Double-click on the field named "Expire Date". -The "Specify Calculation" dialog box will appear. The correct calculation for this field is as follows: Case( Payment For <> "Dues", TextToDate(""), IsEmpty(Start Date),TextToDate(""), Duration = "Indefinite", Names::gToday+730, Min( Date( Month(Start Date) + If(PatternCount(Duration,"M"),TextToNum(LeftWords(Duration,1)),0), Day(Start Date), Year(Start Date) + If(PatternCount(Duration,"Y"),TextToNum(LeftWords(Duration,1)),0)), Date( Month(Start Date) + 1 + If(PatternCount(Duration,"M"),TextToNum(LeftWords(Duration,1)),0), 1, Year(Start Date) + If(PatternCount(Duration,"Y"),TextToNum(LeftWords(Duration,1)),0)) - 1)) B) If the calculation for your field reads differently, you should correct it by: -Copying this calculation: Case( Payment For <> "Dues", TextToDate(""), IsEmpty(Start Date),TextToDate(""), Duration = "Indefinite", Names::gToday+730, Min( Date( Month(Start Date) + If(PatternCount(Duration,"M"),TextToNum(LeftWords(Duration,1)),0), Day(Start Date), Year(Start Date) + If(PatternCount(Duration,"Y"),TextToNum(LeftWords(Duration,1)),0)), Date( Month(Start Date) + 1 + If(PatternCount(Duration,"M"),TextToNum(LeftWords(Duration,1)),0), 1, Year(Start Date) + If(PatternCount(Duration,"Y"),TextToNum(LeftWords(Duration,1)),0)) - 1)) -Paste this calculation into the "Specify Calculation" dialog box. -Click the "OK" button. -Click the "Done" button. -You should then select and run the "Replace All Find Fields" script from the Scripts menu, leaving the date blank so that it runs for your entire file. NEW FEATURE: DATA RECOVERY AND EXPORT UTILITY ---------------------------------------------- 9) Added script to assist in data recovery/exporting to new ebase� clones -------------------------------------------------------------------------- Enhancement to ebase disaster recovery process. Added a group of scripts to allow "one button" export of all data from all data fields in all major ebase files to appropriately named comma quote delimited files with the field names in the first row. In the case of a "crash" or similar disaster these exported files can be used to re-load the data into a "Clone" of your database. TO ADD THIS FIX TO YOUR VERSION OF EBASE: ----------------------------------------- A) You will need to add an export script called Export_AllFieldsToMER to each of the major ebase Files. What will be shown here is the process for adding the Export_AllFieldsToMER script to paymnts_102 you will need to repeat the process for the 21 major Files. Note: that the process of adding the Export_AllFieldsToMER script cannot be successfully completed in files without any data in them so you need to add data to some files or skip them. -Get into ebase using your master password. Once you're on the HOME screen, Click on the View payments button to bring you to the paymnts_.102 file. -From the pull down menus select: Scripts ->ScriptMaker then at the Define Scripts dialog box -Type in a new script name "Export_AllFieldsToMER" then click on the "Create" button. -Click on the "Clear All" button. -Add in the step "Show All Records" by scrolling down the left-hand panel to the SORT/FIND/PRINT section and double click on "Show All Records" -Add step "Export Records" by scrolling down the left-hand panel to the RECORDS section and double click on "Export Records" -Click on the "Specify File" button, at the Export Records dialog box set "Save as" type as "Merge Files (*.mer)" and in the Filename field fill in paymnts_102 The resulting saved file will be "paymnts_102.mer". -Make sure that the Perform without dialog check is NOT checked -Click the "OK" button. -At the "Define Scripts" dialog box, click on the "Perform" button. -At the "specify export order" dialog box click on the "Move All" button then on the "Export" button. -From the pull down menus select: Scripts ->ScriptMaker then at the Define Scripts dialog box -Highlight the script named "Export_AllFieldsToMER" then click on the "Edit" button. -Click on the "Export Records" Step and then check the "Perform Without Dialog" choice. -Click the "OK" button. -At the "information needed dialog for "Export Order" choose the REPLACE option. -Click the "OK" button. -Click the "Done" button. - Now repeat this process for the remaining .102 files in the eBase directory. * note for other files the process is the same you should name the exported file using the format "filename_102" for a resulting exported file of "filename_102.mer" B) Create a script to run all of the "Export_AllFieldsToMER" scripts in the various ebase files. -Get into ebase using your master password. Once you're on the HOME screen, -From the pull down menus select: Scripts ->ScriptMaker then at the Define Scripts dialog box -Type in a new script name "993 - Export to MER" then click on the "Create" button. -Click on the "Clear All" button. -Add in the step "Perform Script" from the left-hand panel by double clicking on "Perform Script" -In "Specify" choose "External Script" -At the "Specify external Script" dialog click on the "change file" button -At the "File types" and choose "All Files (*.*)" -If you the dialog does not show your ebase directory use navigation in the dialog to go to it. -Choose paymnts_102 -At the "Specify external Script" script area choose "Export_AllFieldsToMER" -Click the "OK" button. -Click the "Done" button. -Now repeat this process to add External Script commands for each of the Files you added scripts to in art A to the "993 - Export to MER" Script. C) Final step add a button to allow running the "993 - Export to MER" script for the Admin screen. -Get into ebase using your master password. Click on the "Admin" button then Click on the "Screen 2" button, -You will now need to add a button to run the "993 - Export to MER" Script -From the pull down menus select: View ->Layout Mode -Click on an existing button then right click and choose "Copy" -Choose a location for your new button then right click and choose "paste layout object" -Double click on the new button and at the dialog choose "993 - Export to MER" -Click the "OK" button. -From the pull down menus select: View ->Browse Mode ## End of File ## ------------------ Reminder to each recipient: To change your list account preferences, go to http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address you used to subscribe to the ebase support list:: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] --------------------------------------------------------------------- ebase - Relationship Management for Nonprofits, http://www.ebase.org ---------------------------------------------------------------------
