Hi,

The DICT of every data table is used to define "Data Column Attributes".

Some of these attributes relate to data entry validation; some for the display characteristics and column headings for reporting.

Suggestion: can some extra fields be added to the DICT that allow us to specify defaults for things like display alignment (left, centre, right), label/value position (side-by-side, over/under) and prompt text to be used when a data column (field) is specified for a FORM?

In our applications we have always specified what the Column Heading is, usually in mixed case, and surrounded by « and ».

Example: data column is WEBSITE, Column Heading is «Website». On a form I would want "Website" or "Enter Website".

One field is being used for two or three separate purposes, and you have to bite the bullet at some point and accept that the compromise is a poor job. What's needed is a print column heading (the original purpose), a screen column heading, and a screen prompt label. One value can't do all three.

If each DICT had this information, then it could be used in the O4W Form Definition Wizard, on the Edit/Display Tab, as the default for the "Label" column. Specified once (in the DICT) it is standard everywhere it is used! No re-typing / amendment needed!

Could this be done?

Consider using a symbolic to format data, and imbedding the HTML in the symbolic formulae.

So if you want to right align the data in field 4 of the record, your symbolic formula might look like

return "

":@record:""

or, if you wish, another way is using "hard" spaces

return "   " : @record

Eric,

That would certainly handle data formatting; Susan (I think) was wanting to get some more managed handling of the format of the field labels - and rendered differently acording to usage context.

I know what you mean, Richard. But the idea that a symbolic can reformat (or truncate or concatenate or justify) data is one of the crucial advantages of Revelation products. And we often forget it.

I don't know how manipulable the classes are in the code that O4W generates, so I was offering this as one way forward (even as an interim step).

The inherent beauty of variable length data is that it behaves hand-in-glove with HTML (also variable length).

Eric,

Good point. Also alternative label formatting / value formatting can be handled by alias fields ie the master field label might be MYFIELD and the alias might have a label ].

Susan did highlight an issue - seems that we treat the justification for the label the same as justification for data value, dont have independant formatting.

The concept also runs as far as using bold tags for totals, or even different cell background colors for different rows and columns.

G'day Susan,

I use the User Defined fields (positions 41 - 45) in the dictionary for this exact purpose. Built my own window to edit the data. Works a treat.

Dave G

View this thread on the forum...