Re: Strategy for navigation & validation

[Hal DeVore]

>>>>> On Wed Mar 31 20:58:43, "Bob" == Bob Ebert wrote:

  Bob> Sometimes you're just better off with a simple-but-
  Bob> annoying solution. :)

Hm... I thought there was one solution that was not annoying and 
didn't leave the possibility of lots of incomplete data.

Allow exactly ONE record to be incomplete.  Don't allow a new
record to be started (or the current record to be marked "done")
until all fields are filled in.  You could hold this one record
in a "known" place in the database (index number 1 or something).

But DO allow your app to exit with an incomplete record.  That
lets the user do things like access the calculator and preserves
"Zen of Palm" app-switching-in-lieu-of-multitasking.

And when it's restarted, if there's an incomplete record bring 
it up and take up where you left off, forcing the user to 
complete or cancel the partial record.

-Hal <*> A conclusion is simply the place where you got tired of thinking.