Alltime Data Loss Issue

[markgr]

Let me begin by saying that I've been using prior versions of Alltime for over 4 years. I'm a lawyer, and keeping track of my time is how I get paid, so trusting my business to Iambic for this period of time is no small matter to me.

I recently upgraded to Alltime version 4 and just bumped up to 4.07. I'm using a Tungsten T3. I wish it was possible to still use version 3.21.

The most critical problem I have noticed with version 4 does have a workaround, but it's a data loss issue, which is a big problem for a time capture application.

Here is how you can recreate the problem: Go to the Time Entry screen, complete an entry (i.e. identify a client, matter, etc.) and start the clock. Do not hit "OK." Instead, leave the application, such as by hitting the home key on your Palm. Then return to Alltime. Your new time entry no longer exists and the data is gone.

This can be a huge problem if you've simply started an entry and gone about your business for several hours, only to discover the software failed to capture your time.

The workaround is to simply hit "OK" immediately after you start a time entry. If you forget to do this, it's at your own peril.

This sort of problem should be fixed. Data loss goes directly to the value proposition of the software, and users shouldn't be able to lose their data this easily. I hope we see a fix for this soon.

I have other concerns about the software, which are less significant gripes. Although I usually never post criticism of products, I'm doing so because (a) Alltime 3.21 was so valuable to me; and (b) others should known about these issues before giving version 4 a try.

Mark Grant

[hayne@sympatico]

I (unfortunately) independently discovered the same data loss issue that Mark explained.
I am using version 4.09 on a Tungsten T3.

I came to these forums to see if anyone else had reported this huge bug in AllTime.
I am somewhat dismayed to see that Mark had apparently reported this bug (via these forums) back in December 2003 and it has not been fixed in the 6 intervening months and two point versions.

This issue is (as Mark mentioned) a critical fault in a time-keeping application. Users in a hurry (a large majority of those using AllTime for time-tracking I imagine) will often forget to press the "OK" button as suggested in Mark's work-around and thus it is likely that many others will experience data loss - often without realizing it.

If the developers are finding it difficult to fix this bug in the correct way (keeping the dialog open and running and return to that dialog when AllTime is again made active), I suggest that they should make a tap on the "clock" be the same as a tap on the "OK" button. This would be a loss in functionality but at least would prevent data loss.

[ajenkins]

I'm using AllTime version 4.10 on a Tungsten T3, and it still has this bug. I've been bitten by it a few times already, though I usually remember to hit OK before switching to another app.

[JohnAlbin]

Just a reminder that Iambic has chosen NOT to fix this critical bug. (If you start a timer, and then switch to a new app before hitting OK, you lose your data.)

Version 3.x did not have this problem. And since AllTime 3.x did not lose data in this manner, there is obviously no technical reason why Iambic can't fix this problem. However, Iambic claims that version 4.11 works this way "by design."


P.S. There are currently 123 threads in this forum. So be sure to change the settings to see ALL unresolved problems: "Display Options"->From the: "Beginning->"Show Threads"

[JohnAlbin]

Still no reponse from Iambic support. 1 year and 7 months and counting...