Gary

Sybase SQL Anywhere Studio has all the tools you need to deploy this type of app. I use ASA (Adaptive Server Anywhere) as the database, Mobilink (ML) to do the replication. I use ODBC to connect to the data but the do have an OLEDB provider. ML is a hub and spoke system. All data moves to the consolidated database and back out to he remote databases based on the rules you setup. The consolidated can be a number of different databases including MS SQL and Oracle. ML has two way replication capabilities. In other words, you can enter data at either the remote db or the consolidated the data will move to the proper databases according to the user defined scripts. There a number of events that can be used to manage data conflicts down to the column level.

>1. Head office SQL engine (main data set).
This is the consolidated db

>2. (Multiple) Remote office SQL engines holding the same data as Head office so they can work offline if links to head office are lost.
This is what it does best. It will also run on laptops so you can have laptop users work disconnected and then replicate back to the consolidated database when back in the office.

>3. Any jobs entered into local office are synced back to Head Office.
Yes.

>4. Jobs entered into Head Office from head office itself (or other local offices) are synced back to all other local offices.
Yes. There are events that can be used to handle data conflicts.

>5. Does sybase offer some solution for handling PK's generated in remote locations that will be synced back to the master database (that can carry on if the lines are down between remote and head office).
ASA has a couple of options. The one I use is call Global autoincrement defaults. This is an integer data type that combines an identity with a database number. For example, you can define a PK as a global autoincrement(9999999) and the database number as 10. Then each key will be with 100000001, 100000002 ….

>6. In this kind of scenario, are the tools including the databases distributed royalty free after you have purchase the sybase tools or, do the sites still have to licence the databases etc.,
Each database has to be licensed as well as each client. Sybase does have OEM programs if you have a log of customers to distributed to . The cost is much less then MS SQL.

>7. How do you routinely connect to the backend using VFP? ODBC, ADO ?
ODBC

>8. Syntactically, how close is sybase to SQL server in the T-SQL type language implemetation stakes?
I have not used MSSQL for a few years but I have been told that it is very compatible to TSQL. I personally use the ANSI 99 standards but I think that is mainly what I am used to. I have been told that the ANSI 99 syntax is more powerful but I personally could not attest to that.
>
>I hope you don't mind so many questions!
>
>This may be an ideal solution for a problem I am aware of <s>.
>
>Thanks!