to play devil's advocate, what if i have to enter 50 records, but i don't
know the ZIP code offhand and i need to ask so-and-so who's not available
until tomorrow. it sure would be nice to be able to enter those 50 records
and fix them up later.
but there are lots of ways to handle this, which fit in with Hal's
suggestion just great.
for instance, when you start the app, detect if there are any incomplete
records, and prompt the user. or, every time you enter a new record if
there are incomplete records you can prompt. you can also use a "Don't show
me this again" style of alert to make it slightly less annoying. (anyone
want the code for this kind of alert? i have it.)
but......... why can't the conduit pop up UI during the sync to alert the
user that they have incomplete data that is not being sync'd? that seems
like a Zen-compatable approach and also gives fair warning in your face that
there is incomplete/unsyncable data. obviously conduits can bring up UI b/c
several do -- and IntelliSync can pop up modal UI (if you enable that
option) to ask the user how to resolve a conflict during syncing.
-----Original Message-----
From: Hal DeVore <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Wednesday, March 31, 1999 7:42 PM
Subject: Re: Strategy for navigation & validation
>
>>>>>> 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.
>
>
>
