The SMAT DB was introduced in a earlier version 6.1 I blieve (or maybe 6.0, can’t remember which one). Anyway, it allows there to be a single file for your SMAT messages that get saved. I can tell you that we are using it and it runs much faster and uses less space that .idx and .msg files.
It does take a bit more to get used to but I feel it is a great improvement.
When you enable SMATdb encryption, the engine uses (at this time) the sitename as the encryption passcode. There is a request to Infor the make the passcode configurable, but I do not know if/when we will see this feature.
In the meantime, you can use the hcismatdb tool (available from this forum) from Charlie Bursell to pull out messages into a file. With a little change, you can make the passcode a user supplied arg to make the files more portable.
Since the encryption is really built into SQLite, you can write your own scripts to handle most situations. I even have a script I use to migrate encrypted smatdb’s from site to site updating the passcode on the fly.
Cloverleaf 6.2 allows you to specify your own encryption key for SMATDB. This means you can choose to synchronize the encryption key across all sites and use a more secure key than site name. Excellent enhancement!
.
.