Hi Andy [...] > associated nodes, then there are no associations for that schedule. But > maybe the original developers of the QUERY ASSOCIATION command thought it > would be useful to show you which schedules had no associations. [...]
That was exacly the reason, why I noticed the difference: I was looking for a (fast) select statement, which shows defined schedules which are not associated with any node (maybe simply forgotten or maybe on purpose, e.g. to assocate them later). So it seems I have to use a (slightly?) more complex statement. Thanks for your answer, Andreas
