>>>>>(Why I have integer surrogate keys in the first place is not my fault-I'm maintaining and can't change the base tables).
>>>>>
>>>>>I need to work with tables offline. So:
>>>>>-I create a separate view with only view definitions in it (one table-one view).
>>>>>-Take them offline to a mobile place.
>>>>>
>>>>>When they need to be updated is there a way to do that just using tableupdate() or alike instead of checking per table (using getnextmodified) and doing record by record insert/update/delete?
>>>>>Browsed all documentation about it + some tests to no avail:(
>>>>>TIA.
>>>>>Cetin
>>>>
>>>>add a ts
>>>
>>>Nice Fabio I even wanted to add a GUID but where:)
>>>Cetin
>>
>>ts is a timestamp, GUID is a global id and id is a table's id .
>>
>>I have not understood what you have to do,
>>but ts it is necessary.
>>
>>1) Want you implement a
>>master/slave replication
>>or
>>peer to peer replication ?
>>
>>Where do the changes happen?
>>
>>Will The tables have a primary key, correct?
>>
>>The views are created with CREATEOFFLINE ?
>
>OK let me try to a bit more clear:
>
>TableA, TableC,...tableN all have integer primary keys generated via stored proc (modified version of NewID()).
>
>Tables have PK-FK relationships.
>
>I need to take them offline, work on them and get back.
>
>Let's sample with testdata.dbc:
>
>A new customer is inserted offline. Key is not yet known (will be assigned later, only have a key which is valid in offline set).
>
>Multiple orders are inserted for this customer. Again keys are valid for offline set, also FK cust_id is locally valid.
>
>Per each order orditems are inserted using locally valid FK.
>
>Now when this data gets back to online would this work (actually up till now I didn't use views so not sure-testing different scenarios):
>If I create the PK-FK relations with cascade in views before I take them offline, use online exclusive, tableupdate(). Would all tables get correct PK-FK generated on master db? This would need a special care on the order of tableupdates but I can handle it ( around 120 tables:( ) if that would work.
>Otherwise what I do is to:
>Take an offline view (use online exclusive):
>GetNextModified loop.
>insert/update.
>Get pkey assigned
>Update FKs in referenced tables.
>
>Hope it's understandable now.
>Cetin

Offline is offline
( an offline view cannot know the master db history, it is a snapshot only ).

A way:
Into offline tables or local view generate negative id,
this respect the order and don't overlap the pk domain in master db.

But if you use GetNextModified , then it is not an offline view,
it is a local view only.
A offline view is a local table,
and you can close the process and sync the master db
when the application allocate another process ( after a month ).