App Sync, Must the Tables and fields name be the same?

[KC Chin]

Hi,

NetTalkApps.Htm Introduction,...
"In some ways this means thinking "beyond SQL". SQL has traditionally been the store of choice for many programs, and indeed there are many benefits to having SQL as a store, but data inside a SQL database requires clients to connect to that database. In order to create disconnected programs we have to allow the data to escape the SQL database, returning (possibly changed) at some later point. Of course this does not replace the SQL database - your primary store will likely remain as a SQL database (although it could also be TPS) - but rather it expands the horizons of the database."

Must the Tables and fields name be the same where Server is SQL, and Desktop app is TPS and XML when Sync App Disconnect?

[KC Chin]

Hi Bruce,

"Must the Tables and fields name be the same?"

What I am trying to say is ...

SQL and TPS Tables and fields

Both tables have same field name except the TPS where there are 4 extra fields than the SQL table.
Both table's name is different by a single letter "Z"
Table name "CSAGT" and "CSAGTz.tps"

CSAGT table (sql server)
field_a long
field_b string
field_b string
... more fields
TimeStamp
ServerTimeStamp
DeletedTimeStamp

CSAGTz.tps table (topspeed)
field_a long
field_b string
field_b string
... more fields
... plus extras
field1 long
field2 long
field3 string
field4 byte

TimeStamp
ServerTimeStamp
DeletedTimeStamp

Questions before I mess up my dictionary and Client app:

1. How to sync from Client(Desktop)  to Server(WAN) with the above situation?
2. For Client(Desktop),
    Do I separate Dictionary just to solve it like change the table name to the SQL side "CSAGT" instead of "CSAGTz.tps"?

Regards,
KC

Answer for #2. I think I just answered my very own question.  table{prop:name} and table{prop:driver}
Answer for #1. still work-in-progress

[KC Chin]

1. Oh well, back to drawing board again.
2. Now, split into 2 dictionaries. SQL and Topspeed(Desktop Disconnect) separately.
- and use the same table name to do the sync.

3. Less headaches and less coding.  Just let NetTalk do the working. 
4. Luckily it is just a 4 tables(Topspeed) instead of almost a 100 tables (from SQL side).
5. 4 tables is easier to maintain if there are some changes from the SQL side.
6. Hopefully and cross my fingers than only 4 tables to maintain.

Cheers for those who are reading my self reply messages.

[Bruce]

Hi KC,

>> "Must the Tables and fields name be the same?"

yes.

(It doesn't matter if one table has extra fields, those fields are just discarded during the sync.)

Cheers
Bruce