1.  After Installing CookBookPlus Desktop 2008 please visit the Microsoft Update web site and install all applicable updates.
http://www.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us     [Posted 7/23/07]

2. No apostrophes - If you use apostrophes while entering data into CookBookPlus, some of the queries will fail. 

3. Graph charts will fail to display data if, on any given day, some, but not all, meals are “checked off” on the Daily Calories Report. Example: You log your meals and then “declare” (by using the “All” button on the Calendar) that the logged meals represent all food consumed for that day (See Video 16 for instructions). Then, after doing so, you subsequently enter another meal or snack for that date, and you DO NOT again “declare”. Not declaring again will leave the initial meals “checked off” but the new meal “will not be checked off”. If you try to produce a graph chart (Calories or % Fat), the chart(s) will appear blank, and you may receive an error message that the “component is not working properly and needs to be repaired”. To fix, just reproduce the Daily Calories Report for the day in question, and click the “All” button on the Calendar; this will “check off” all meals/snacks recorded for that date. Re-run the graft function(s) and the chart(s) should show the correct data.

4.  CookBookPlus Desktop 2008 (Access 2007 Runtime version) and minor incompatibility with Office 2002/full version Access 2002.

We have successfully installed CookBookPlus Desktop 2008 that works with the Access 2007 Runtime on a Windows XP SP2 PC with a full version of Office 2002/Access 2002 already installed.   CookBookPlus 2008/Access 2007 Runtime ran normally.   We then launched a non-runtime Access 2002 database using a desktop shortcut.  That application opened OK, and ran OK, but it was, for some reason, being run under the Access 2007 Runtime.  Accordingly, the color schema of the database was changed somewhat.  We fixed this obvious file association issue by closing the 2002 database, opening Access 2002 full version, and opening the database again from within Access 2002; it opened normally under Access 2002, and looked normal.  Subsequent openings of any non Runtime Access 2002 database would result in a "Office XP is being configured" dialog that would shortly close with the 2002 database opening normally under full version Access 2002.   This is a known compatibility issue with Access 2007 Runtime and previous versions of full version Access that we understand is being addressed by Microsoft (Office 2007 SP1?).  We consider this to be a minor inconvenience.  [Posted 7/23/07].

This same PC also has CookBookPlus Desktop 2005/Assess 2002 Runtime installed.  The Access 2002 Runtime version of CookBookPlus ran fine with no apparent compatibility issue.

We have successfully installed CookBookPlus Desktop 2008 that works with the Access 2007 Runtime on a Windows XP SP2 PC that does not have any full versions of Access installed.  This test PC had both CookBookPlus Desktop 2002 and CookBookPlus Desktop 2005 in side-by-side installations; both versions use the Access 2002 Runtime.  All 3 versions of CookBookPlus ran fine with no apparent installation compatibility issues.

CookBookPlus Desktop 2008 (Access 2002 Runtime version) and minor incompatibility with Office 2007/full version Access 2007. 

We have successfully installed the version of CookBookPlus Desktop 2008 that runs under the Access 2002 Runtime on a Vista PC that did not have Office 2007 installed.   The CookBookPlus Desktop 2008/Access 2002 Runtime program ran normally.   We subsequently installed Office 2007 on that Vista PC and the previously installed CookBookPlus Desktop 2008/Access 2002 Runtime continued to run normally.   However, after running CookBookPlus Desktop 2008/Access 2002 Runtime, if an Office 2007 application was subsequently launched, an Office 2007 dialog would appear indicating that "Office 2007 was being configured".   After the dialog closes, the Office 2007 applications run normally. This is a known compatibility issue with Office 2007 and previous versions of Access Runtime that we understand is being addressed by Microsoft (Office 2007 SP1?).    We consider this to be a minor inconvenience.  [Posted 7/3/07].