Edit tables and multi value fields in 4.1.3 (OpenInsight 32-bit Specific)
At 11 MAR 2003 03:20:57PM S Botes wrote:
I have noticed that in 4.1.3 when I have an edittable column that is tied to a database column and the column in question has three levels of MVs, (1,1,1),(1,1,2) for example, that the only value that is evident in the table is the first component of the first field only.
In my specific case I have a data string that looks like this: Item1 @VM RG*1234 @SVM RG*2345 @SVM RG*3333. The only item that appears in my table on the read or after a get_property is the field containing ITEM1. The rest just disappears.
Am I wrong or has this changed since previous releases. And what is proper? If the edit table is only going to have the first value then all subsequent data will be truncated on a read write step won't it?
At 11 MAR 2003 03:32PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Steve,
As far as I'm aware the edit table has never supported @svm'd data - it's always truncated at the first @svm and yes, this will write truncated data to your tables.
World leaders in all things RevSoft
At 11 MAR 2003 04:04PM S Botes wrote:
Thanks for the quick answer…
At 12 MAR 2003 06:00AM Oystein Reigem wrote:
Steve,
You might want to consider this suggestion: .
- Oystein -
At 12 MAR 2003 08:23AM Richard Guise wrote:
Depends what you want to do with the data.
As with mv long text fields, the trick is often to store the whole field in a hidden edit prompt and then work from there.
E.g. we have edit tables of events with dates, type codes, etc. plus notes for each event. All but the notes are handled traditionally but the notes are stored separately. When a notes cell is double-clicked the appropriate mv is extracted into an overlay editor. When saved it's popped back.
Also sometimes instead of notes we have makeup tables for each event, using svms, etc. and similar technique can be used.