"Christophe Beauregard"
<christophe.beauregard@sympatico.ca> writes:
What about letting the Handheld assign its own
record id and the Server use its SQL ids, and
then, for each Handheld, have a SQL table
containing (Database,hhID,sID), where Database is
the name of the Handheld database (DatebookDB,
etc), hhID is the handheld record ID for that
database, and sID is the server record ID (which
might be database specific or it could be a
global ID).
If, when you "sign up" a new user, you check his user
id against the current user list. If their id is
unique, then userId+recId _IS_ unique guaranteed!
Across all devices. I guess I am still a little in
the dark where the "multiuser" difficulty comes in.
Personally I would be more than willing to change my
user ID. But muck with record IDs and IO the record 3
times ... not so much.
Despite all the "resistance" you are getting, it
sounds like a great project. Which is probably why
this thread is so long! Maybe you could put up a
couple of screen shots somewhere of what you are
developing.