Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 15 APR 2009 11:04:43PM Martin Drenovac wrote:

Is there a "@USER" style field within the dictionary items that I can use for internal purposes? ie. not-used by OI?

I want to manage DICT driven XSLT conversions.

Cheers


At 15 APR 2009 11:28PM dbakke@srpcs.com's Don Bakke wrote:

Martin,

If you check out the DICT_EQUATES you'll find these equates:

EQUATE [/color]DICT_USER1$              [/color]TO [/color]41     [/color];[/color]* This field is reserved for the application. 
[/color]EQUATE [/color]DICT_USER2$              [/color]TO [/color]42     [/color];[/color]* "" 
[/color]EQUATE [/color]DICT_USER3$              [/color]TO [/color]43     [/color];[/color]* "" 
[/color]EQUATE [/color]DICT_USER4$              [/color]TO [/color]44     [/color];[/color]* "" 
[/color]EQUATE [/color]DICT_USER5$              [/color]TO [/color]45     [/color];[/color]* ""[/color][/color][/size]         
               

Keep in mind, however, that DICT.MFS will prevent you from updating these fields in a strict runtime environment. It will also prevent field position 28 (DICT_MASTER_FLAG$) from being written to and field position 35 (DICT_TIMEDATE$) will be overwritten. Other than that you should be fine.

dbakke@srpcs.com

SRP Computer Solutions, Inc.


At 15 APR 2009 11:31PM dbakke@srpcs.com's Don Bakke wrote:

Martin,

The comments about fields 28 and 35 were included in case you choose to create a custom dictionary record. In your case this is probably irrelevant since you are using user reserved fields for existing dictonary items. Sorry for the confusion.

dbakke@srpcs.com

SRP Computer Solutions, Inc.


At 16 APR 2009 07:26PM Matthew Crozier wrote:

Be careful of DICT_USER5 though!

Cheers, M@

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/56c70cfa7a210bd18525759a0010e993.txt
  • Last modified: 2024/01/04 20:57
  • by 127.0.0.1