Hi All!

I read the discussion between Oystein, Don and a couple of other people about Subvalues in Edit Tables. I have suddenly found that I may well have a need to use Subvalues (does the fun never stop?), having never had to worry about them before. I understand that Subvalues don't work particularly well with Edit Tables but could someone describe in what way they don't work well? Perhaps it is something I could live with. My other option, following long the lines of the previous discussion, would be to simply use commas or other delimiter, but I would rather be able to use BTree indexing on these fields.

The suggestion to use a symbolic instead of the true data for these @SVM fields would be fine except that I'd rather not force the user into additional keystrokes or mouse-clicks to enter multi-subvalue data.

Any suggestions?

Thanks,

Fr. Mike

Mike,

We found that if the control was tied to a database record then we had to swap the subvalues for some other delimiter and then swap back on the write….

It seems to me that when we supplied that data with our own read tnd then used set/get property the problem disappeared. That probably should be verified…

Mike

Subvalues and a two dimensional Edit Table don't really get on.

The fact that we have Sub-values goes against most of the world, and this is fair given that edit tables are two dimensional and this is what users interract with.

When handling such things, I have added two edit tables to the form, with the top table being the fields and MVs, and when a row is highlighted, you populate the lower table with the relevant SVs.

This is of course not a database associated table, but a manually managed update.

If doing this, it is best managed in COMMON variables.

Another possibility is to 'normalise' (a horrible term) your data into the edit table, and re-subvalue it when you save, but to do this you have to write all the data when the user saves, and not individual records as they update, which is messy.

Colin

Mike,

Say you have an edit table cell that contains "aaa" : @SVM : "bbb". This will display as "aaa bbb". But when you save the row only "aaa" is saved.

I now use @TM instead of @SVM. "aaa" : @TM : "bbb" displays as "aaa

bbb". If the field has a Btree index both "aaa" and "bbb" get indexed.

(I don't let the user enter or see the "

". The user interacts with the data through a different control.)

- Oystein -

Mike,

Say you have an edit table cell that contains "aaa" : @SVM : "bbb". This will display as "aaa bbb". But when you save the row only "aaa" is saved.

I now use @TM instead of @SVM. "aaa" : @TM : "bbb" displays as "aaa

bbb". If the field has a Btree index both "aaa" and "bbb" get indexed.

(I don't let the user enter or see the "

". The user interacts with the data through a different control.)

- Oystein -

View this thread on the forum...