Re: [pilot-db-list] on the way: DB Conduit / windows / MS Access

[Fab <kr...@bi...>]

> The 'no sync' scenario presupposes a database having
> a single user updating it.
> That's not always the case.  Some databases (for instance, a sales
> based database) intrinsically are updated on both sides.

	Of course, I only spoke about my needs :-)
	But the scenario you evoke is kind of dangerous. There is
absolutly no way to prevent multiple accesses on the same real record
which is logically duplicated through all the pdas. I would prefer
to have the pdas store a readonly database, and news or modifications
stored in another database on the pdas. Then I should use a robust
program on a central machine to include with a lot of controls the
different modifs when the pdas come back home. The idea should be to
record events in the pda, rather than pure modifications of the copie
of the database the pda has in. But the problem is rather tricky.
	Fab.