using DICT file level to document MV

#11

I've often seen attribute 13 used for this purpose.

Almost all of the attributes after 10 are safe. I wouldn't use the
lower ones.

Just don't step on a file defining item, or a resize parameter.

#12

I've often seen attribute 13 used for this purpose.

Almost all of the attributes after 10 are safe. I wouldn't use the
lower ones.

Just don't step on a file defining item, or a resize parameter.

#13

I've often seen attribute 13 used for this purpose.

Almost all of the attributes after 10 are safe. I wouldn't use the
lower ones.

Just don't step on a file defining item, or a resize parameter.

#14

I've often seen attribute 13 used for this purpose.

Almost all of the attributes after 10 are safe. I wouldn't use the
lower ones.

Just don't step on a file defining item, or a resize parameter.

#15

I've often seen attribute 13 used for this purpose.

Almost all of the attributes after 10 are safe. I wouldn't use the
lower ones.

Just don't step on a file defining item, or a resize parameter.

#16

I've often seen attribute 13 used for this purpose.

Almost all of the attributes after 10 are safe. I wouldn't use the
lower ones.

Just don't step on a file defining item, or a resize parameter.

#17

I've often seen attribute 13 used for this purpose.

Almost all of the attributes after 10 are safe. I wouldn't use the
lower ones.

Just don't step on a file defining item, or a resize parameter.

#18

On Nov 6, 6:57*am, Douglas Tatelman <doug... (AT) pickteam (DOT) com> wrote:

Quote:

I've often seen attribute 13 used for this purpose.

Almost all of the attributes after 10 are safe. *I wouldn't use the
lower ones.

Just don't step on a file defining item, or a resize parameter.

Attribute I believe is for resize parameters.

Attribute 14 hold the description or help text in D3 dictionaries that
gets used by the Update Processor

If more attributes are wanted or needed for documentation, I would
experiment with attributes equal to or greater than 31.

Try and find the latest documentation on dictionaries. I do know that
basically all attributes equal to or less than 30 are currently
defined for use with/by the D3 system

Best regards, Dale

#19

On Nov 6, 6:57*am, Douglas Tatelman <doug... (AT) pickteam (DOT) com> wrote:

Quote:

I've often seen attribute 13 used for this purpose.

Almost all of the attributes after 10 are safe. *I wouldn't use the
lower ones.

Just don't step on a file defining item, or a resize parameter.

Attribute I believe is for resize parameters.

Attribute 14 hold the description or help text in D3 dictionaries that
gets used by the Update Processor

If more attributes are wanted or needed for documentation, I would
experiment with attributes equal to or greater than 31.

Try and find the latest documentation on dictionaries. I do know that
basically all attributes equal to or less than 30 are currently
defined for use with/by the D3 system

Best regards, Dale

#20

On Nov 6, 6:57*am, Douglas Tatelman <doug... (AT) pickteam (DOT) com> wrote:

Quote:

I've often seen attribute 13 used for this purpose.

Almost all of the attributes after 10 are safe. *I wouldn't use the
lower ones.

Just don't step on a file defining item, or a resize parameter.

Attribute I believe is for resize parameters.

Attribute 14 hold the description or help text in D3 dictionaries that
gets used by the Update Processor

If more attributes are wanted or needed for documentation, I would
experiment with attributes equal to or greater than 31.

Try and find the latest documentation on dictionaries. I do know that
basically all attributes equal to or less than 30 are currently
defined for use with/by the D3 system

Best regards, Dale