Messages File

Top  Previous  Next

You need an auxiliary file for storing the audit information related with FullRecord, and as header for the "don't ask again" feature.

You can create a DCT-less version of NeatMessage, but then you won't be able to use these particular features.

To disable the usage of files for NeatMessage, you have to tick the "No DCT" option as follows:

 

 

clip0042

 

If you activate this option, no file will be used at all, and neither the Audit feature nor the Don't ask again feature will work.

 

If you don't activate the "No DCT" checkbox (this is the default), you have to fill the following prompts.

 

 

clip0031

 

Messages file: This is the name of the file that will hold the audit information.

You may import its definition into your DCT by copy and paste it from the example, or by importing the neatmessage.txd file from the examples folder.

 

by "ID" key: This is the key of the Messages file that will identify each message by an unique number.

 

by "Message" key: This is the key of the Messages file that will identify each message by its contents (description).

 

"ID" field: This is the field inside the file structure that will identify each message by a unique number. This should be a LONG.

 

"Message" field: This is the field inside the file structure that will hold each message contents (description). This should be a STRING, in our sample file we defined it as 200 characters long, but the length is relative. The shorten it be, the smaller the file will be, but different messages could end mixed if only the first characters are equal (unless you specify a message identification).

 

Important: NeatMessage will "auto-sense" the presence of FullRecord v1.71 and up, and add the necessary code accordingly to audit the messages.