(2011-06-22) New problem discovered!
Problem: Due to the taxonomic revision of a few species in the latest versions, import of files exported with an older version of BugsCEP might not work correctly.
Explanation: Basically a few taxa have been given new taxonomic codes (i.e. moved to another position in the taxonomic order), and when BugsCEP imports files it does not check names against codes and these taxa get lost.
Solution: To work around this problem, delete the CODE column from the file that you wish to import, thus forcing BugsCEP to match the names.
Future plans: Sorry, we don't have the time or money to fix this one in BugsCEP! We will make sure it doesn't happen in the next version.

Known problems:

Downloading

• Internet Explorer (7+) (on Vista?) only downloads a few KB when you click on the download links, and the downloaded file fragment is identified as a corrupt zip archive file.
  Not sure why it does this, sometimes... probably a security measure "for your convenience" from Microsoft.
  To work around the problem:
  Either:
  1) Right click on the download link and choose "Copy shortcut", then paste the copies link into the Internet Explorer address bar (at the top of the window, where web addresses are shown), then press the Enter key. This should lead to a "File Download" message box which will allow you to save the complete zip file.
  2) Try another web browser (e.g. Firefox or Opera).

Installation

• Bugs will not install - it ends up in a repeating loop of restarts and installation screens. This occurs very rarely and we have no real idea why. Please contact Phil for instuctions on how to manually install BugsCEP.
• The BugsCEP setup routine may restart certain Windows XP machines without warning - we have no idea why. Installation functions otherwise, but please close any other programs before installing!
• BugsCEP update overwrites any alterations made by user in previous version. Sorry, but no merging update is available yet. Please export your countsheets before upgrading, and then reimport them. Better export and import routines will be created in the future, and downloads of just the program part will be provided to preserve data when updating.

Getting it running

• Sometimes BugsCEP will install OK, but then crash with a "run-time error" once started. This can have numerous causes, usually relating to Windows security settings. Try downloading this version, unzipping it into the folder C:\BugCEP (create the folder if necessary), and then double clicking the BugsCEP.mdb file from this folder. Note that you probably need to install the runtime version of BugsCEP before doing this.
• If you have Access 2003 installed (or possibly Access XP or versions inbetween the two) then BugsCEP may not run from the Start Menu - and will tell you that it 'cannot find msaccess.exe...'.
  This is because the installed version of Access is not letting BugsCEP use the Runtime Version of Access 2000 that it is supplied with. You should be able to open BugsCEP directly using the installed version of Access rather than the Start Menu shortcut.
  Either:
  • Find the BugsCEP program file (BugsCEP or BugsCEP.mdb) using Windows Explorer or 'My Computer', and double click on it.
    It is normally in the folder 'C:\Program Files\BugsCEP', unless you chose another one.
  • Open Access, and then open the BugsCEP program file from its installation directory (see above).
• If you have Access 2007 installed then you may encounter problems, including the lack of toolbars which allow the different BugsCEP components to be used. As yet this issue is unresolved, although does sometimes appear to solve itself!
• Under Windows Vista a number of problems may occur, including crashes during first run or during particular BugsCEP operations. Most likely we will not have time or resources to fix these issues and you should try to find an XP machine. BugsCEP will eventually be incorporated into SEAD (http://www.sead.se) and made available online, which will hopefully resolve these issues.
• If you are running Access 2007 under Windows Vista then BugsCEP may or may not run! Please try the alternative Vista frontend, and start BugsCEP from its Start Menu item rather than by double clicking on the database file. (This problem is probably due to the way Vista restricts access to the Windows registry).
  

Operation

• "Error 3027: Cannot update. Database or object is read-only" (or similar).
  If BugsCEP crashes it can leave so called "locking files" behind which prevent you from saving data when BugsCEP is openned next time. The files will be called BugsCEP.ldb and/or bugsdata.ldb, and be very small 0KB - which distinguishes them from the much lager database files (>19MB). Close BugsCEP if it is open and delete these locking files (called "Microsoft Office Access Record-Locking Information" in some versions of Windows/Office).
• After clicking a button or choosing an option from a menu, BugsCEP no longer responds, but no error message is shown. Sometimes pop-up windows are opened at the edge of or even beyond the edge of the visible area of the screen(!). Try pressing Alt+[space]+x which should force the troublesome window to cover the entire screen, then continue as if nothing had gone wrong.
• On some systems, the [Find Next] button does not work when searching the bibliography. At the moment we have no explanation or solution for this problem! It seems to be dependent on something in some Windows installations that we cannot track down...
• On versions downloaded before 6th December 2006, the version numbers displayed on the 'About BugsCEP' screen and in exports was wrong.
• The message "Please close Excel before running the ... routine" is displayed when I try to use BugsMCR or BugStats, but Excel is not open. Either (a) you do not have Excel installed, and cannot run the routines, or (b) Excel has not closed properly and is running in the background. If the latter is true then use the Task Manager to end the Excel process and try again.
• Attempting to delete more than one sample at a time in the Countsheet Editor may cause a crash. To work around this, delete one sample at a time, applying changes between deletions.

Results & Exports

• Using the "To species id's only" option for EcoFig creation leads to incorrect results/sample names under certain circumstances. The problem occurs where a sample only contains low resolution species (i.e. sp./spp./indet.). This is most likely a result of the following:
• Ecofig diagrams include a series of samples called "0" at the bottom, and results (bars) are assigned incorrectly in the diagram. This problem occurs when Bugstats encounters samples with no taxa (i.e. empty samples). Use the samples manager to delete these samples and create the figure again.
• Vertical axes on MCR diagrams are usually different. Sorry, can't do everything. Please rescale them manually.
• Where ln(n+1) transformation is used the SumRep values in EcoFig outputs are incorrect, and hence the '% sumrep' calculations are incorrect when used with this option. We're working on this problem...

Please contact us at the address below if you encounter any other problems.

Data queries: paul.buckland (at) bugscep.com

All other queries and help: phil.buckland (at) arke.umu.se