MobiLink Synchronization User's Guide
Adaptive Server Anywhere Clients
Creating a remote database
It is common for remote databases to fall into separate categories, each with their own requirements. Consider a sales application. All the sales personnel in one region may require access to a particular set of data, but not require access to information about regions other than their own. Employees in other departments may require data of an entirely different nature. Managers may require data that should not be accessible to their subordinates.
Publications are typically used to specify fundamentally different sets of data. For example, you can create one publication for the sales staff and another publication for those employees who do technical support.
You can further fine-tune the data any given remote database will receive by using a WHERE clause within the publication. This feature is useful when remote databases require similar types of information. For example, it can be used to provide sales representatives with only the information relevant to their region.
For more information, see Partitioning rows among remote databases.