>Can you also share your technique to handle any update conflicts? What I mean is, I don't know if it's relevent in your situation but how do you handle a situation where a record contained in an off-line view is changed and when "reconnected" the original record have also been changed since last connection? You would have to "accept" one or none of the changes?
>
depending on the situation some conflicts are resolved automatically (ie according to date or user level)
and in some cases the decision is left to the user who does the update - ie he gets a screen with the 2 records (local and his own) and chooses which is correct
note that in certain cases when you replicate the data it is worthwhile to make 2 copies (one that will not be touched)
then when doing the updates you can resolve conflicts on the field level instead of the record level

Arnon