Hi, I want to include some dynamic dropdown lists in my application using
related records from several tables... (Using 8.5 advanced on Win btw)

For this I have created a calculated field in the parent table wich creates the
dropdown list by using several 'list' commands and by adding some other fields
too. Then I created a relationship between the parent table id and the id of a
2nd entity of the same table to be able to create a value-list using 'related
values only'.

This works like a charm but since the dropdown list is based on a calculated
field I get the warning (while defining) that the list is based on a calculated
field and can therefor not be indexed. Will this cause problems somewere down
the line? (like when on different platforms, runtime etc.)

Are there better solutions to this problem?

Thanks,
Sargasso

"Sargasso" <no.way (AT) ho (DOT) se> schreef in bericht
news:46371130$0$31919$dbd45001 (AT) news (DOT) wanadoo.nl...
Normally it will not create a problem. In a way indexing is a way to speed
up a find. When the index can not be made, you can still search on the
field, but it might slow down the search. If the valuelist is very large
(say over a couple of thousend items) you might notice a slight lag. If the
list is mega-large (over 10000 items) you will notice a lag. But the search
will be performed anyway.

There are ways to overcome this, but all these take some time. Some of them
take time each time the list is changed, others only when you start a
search. In my opinion it is not often worth the trouble. But yours might
just be such a case, this is up to yourself to decide.

Keep well, Ursus

Ursus,

What you say makes sense. Since the list commands used in the calculated field
CAN use the available indexes and I have no intention to search on this field
the only thing that can take some time is sorting the resulting valuelist. But
since I do not expect this list to contain more then about 20 to 30 items this
should be covered also ...

Thanks for your reply,
Sargasso

In article <46371130$0$31919$dbd45001 (AT) news (DOT) wanadoo.nl>, Sargasso
<no.way (AT) ho (DOT) se> wrote:

The parent side of a Relationship can be a Calculation since it doesn't
need to be indexed.

The child side can NOT be a Calculation since it does need to be
indexed.

Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)

No relationships are made to the calculated field in this case. The field is
only used to calculate the combined results of the list commands.

but thanks
Sargasso

No relationships are made to the calculated field in this case. The field is
only used to combined the results of the list commands.

but thanks
Sargasso

In article <4637b4c6$0$31919$dbd45001 (AT) news (DOT) wanadoo.nl>, Sargasso
<no.way (AT) ho (DOT) se> wrote:

Oops! Sorry. I misread the original message in the rush to log off and
get out the door to an appointment. \

Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)