The major bug that appears on these palmOne platforms (the only ones that I know of) seems to be fixed.  There are still other problems that need to be addressed before an official release but they are mostly minor.  If you are using one of these devices with PalmLog PRO, please download and try the test program below.  The same problems are being worked in the basic version(s) of the logbook but another issue with changing dates needs to be fixed before a test program is usable.

Download Links
(Temporary)

Several major network providers seem to be blocking support emails as SPAM.  This was apparently due to the mass mailing of PRO v1.2 codes sent out awhile back.   If you have sent emails and have not received a response, check your SPAM filters and allow emails from helpdesk@frontbeach.com, or better, all emails from frontbeach.com in case they come from sales, webmaster, etc.   AOL and Earthlink seem to bounce/block emails more than others so check your settings if you are on those servers, but check even if you are on another.

The forum is offline while issues with it are being worked. Accessing it was returning a 500 error (Internal server error). Unfortunately, the FAQ and Download pages are tied closely to the forum. The FAQ information cannot be easily reproduced until the problems are fixed, but the Downloads page will show this home page with temporary download links on the right.

For anyone that links to these files (and for the product download links and the ones on the right), I have written a short script to emulate the download while bypassing the forum. This should ensure that all downloads continue to function normally although the download description page will not be shown and the file will automatically download. A future fix may change the download links to bypass the forum but will probably be a different url. I will attempt to maintain backward compatibility to prevent broken links.

It has been reported that the T5 (and probably other devices runnning the same version of the OS) exposed a bug in the various versions of PalmLog (PRO and FBFLv2.x). It is unknown whether the bug also occurs with the older free version but it is highly likely (that version has other bugs related to v5 & higher of the OS).
Here's a description of the problem:

When editing an existing entry (or creating a second entry) you receive a "fatal error"
"DataMgr.c, line: 5630 Record is busy when it shouldn't be".
RESET: reset fails, and a soft reset is required on the Palm and that dumps ALL of the the data in the program.

I am working on this problem and hope to have a resolution soon as it affects several versions so the offending code should be easier to find.

As many of you know, I have fallen behind on support emails and have forgotten to respond with followups in several cases. Because of the volume of email and this being a one-man shop, I am looking into methods to rectify this problem. I plan to setup a "Support Ticket" system that will operate via email (probably to helpdesk) and/or the website. This should help me track support issues and not forget responses since I would have to manually close them. The tickets will allow me to support more issues than the forum and possibly generate a knowledgebase to enhance the FAQ.

This new system will probably coincide with a move to a new service provider/server.