This has now been fixed, there is no longer a problem delivering messages from a 9.0.2 server to a 9.0.1 client in the presence of server-side transmission rules.

If the server-side transmission rule for the 9.0.1 client is removed, the messages would then have been delivered normally. The messages destined for the 9.0.1 client would have remained on the server indefinitely. QAnywhere 9.0.1 clients can synchronize messages with QAnywhere 9.0.2 servers, but if there was a server-side transmission rule for a 9.0.1 client then messages destined for the 9.0.1 client would never have been delivered. The SPACE() function in UltraLitre Dynamic SQL would have accepted a negative value. When backing up a database to multiple tapes, after the first tape had been written, the request for the next tape would have failed. In furthering compatibility with Adaptive Server Enterprise, the following examples now return errors, since they contain invalid hexadecimal characters. The server will now consistently return -9 for the result. The server would have returned either -9 or a conversion error from the following query, depending on the platform: Private connection profiles were saved properly. If a shared connection profile was created, it was not saved if Sybase Central terminated abnormally after the connection profile dialog is closed. This may have occurred if the transmission rule referred to two or more custom message properties in the same rule and the server delete rules included a reference to one of the same custom message properties.

Server-side transmission rules, including references to more than one custom message property, may under certain circumstances have evaluated as if one or more of the custom property values was null. Intreactive SQL could have reported an 'internal error' if the Import Wizard was used to read data from an ASCII file into an existing table, and there were fewer columns in the file than columns in the table.

Sap sql anywhere 17 download