Just an update to whoever is interested:

My two-DBs solution will probably work out OK.
If you've lost track, that means I keep an intermediate DB apart from the
main DB on the PC, in order to pinpoint exactly what records have been
modified since the last sync.
And it will all be possible thanks to Jeff's awesome
way<http://weblogs.sqlteam.com/jeffs/archive/2004/11/10/2737.aspx>to
compare tables (
http://weblogs.sqlteam.com/jeffs/archive/2004/11/10/2737.aspx).
Just in case that blog will come down some day, here's the gist of his
article:

SELECT MIN(TableName) as TableName, ID, COL1, COL2, COL3 ...

FROM

(

  SELECT 'Table A' as TableName, A.ID, A.COL1, A.COL2, A.COL3, ...

  FROM A

  UNION ALL

  SELECT 'Table B' as TableName, B.ID, B.COL1, B.COl2, B.COL3, ...

  FROM B

) tmp

GROUP BY ID, COL1, COL2, COL3 ...

HAVING COUNT(*) = 1

ORDER BY ID

That shows any row that exists in Table A and that doesn't exist in Table B,
and visa-versa.
It's incredibly efficient because it uses UNION.

I will report back in a few days/weeks to tell you guys if this way is a
convenient way to by-pass implementing the bit-mask system manually.

Jonathan

2008/2/12, Jonathan Carse <jonathan.carse@gmai...>:
>
> Hey Eric,
>
> Yes, we are offering the same solution, and both ways will work fine.
> The difference, as you correctly pointed out, is that your solution does
> writes during desktop activity, while my solution does writes during sync
> activity. It's the same result, you are correct.
> It is a lot easier for me to implement the changes on my conduit project
> than on my desktop project, and that is the only reason I lean towards my
> own solution.
> Another developer working on a different project might find it easier to
> implement the changes on the desktop project.
>
> Our project is aimed at the home user. So an SQL server solution seems
> irrelevant - no home user will accept software into his/her home based on
> the condition that an SQL server is installed as well.
>
>
>

--
For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/