Somemessage systems, including SMTP, VIM, and MAPI, require
text-basedmessage formats. Forthese systems, an encoding DLL
(

dbencod.dll

forAdaptive Server Anywhere and

ssencod.dll

forAdaptive
ServerEnterprise) translates messages into a text format before sending.
Themessage format is unencoded at the receiving end using the same
DLL.
Youcan instruct SQL Remote to use a custom encoding scheme. The
toolsfor building a custom encoding scheme are described in the
followingsection.
Ifthe COMPRESSION database option is set to -1, then a Version 5
compatibleencoding is carried out for all message systems.
Creating custom encoding schemes
Youcan implement a custom encoding scheme by building a custom
encodingDLL. You could use this DLL to apply special features required
fora particular messages system, or to collect statistics, such as how many
messagesor how many bytes were sent to each user.
Theheader file

dbrmt.h

,installed into the

h

subdirectoryof your installation
directory,provides an application programming interface for building such a
scheme.
Toinstruct SQL Remote to use your DLL for a particular message system,
youmust make a registry entry for that system. Theregistry entry should be
madein the following location:
Software
\Sybase
\SQL Remote
\message-system
\encode_dll
wheremessage-system is one of the SQL Remote message systems (file,
smtp,and so on). Youshould set this registry entry to the name of your
encodingDLL.
Encodingand decoding must be compatible
If you implement a custom encoding, you must make sure that the DLL is
present at the receiving end, and that the DLL is in place to decode your
messagesproperly.
236