>>>Seems to me that it's confirming that a bunch of tables can be found. It's starting with a list of tables it expects to find (csrTblOrder), and going out to confirm their existence, marking those it finds as processed.
>>>
>>>Tamar
>>
>>Right, but in general that doesn't look too useful to me. Anyway, we're re-writing this application, so I don't want to look too close into this form.
>
>It isn't too useful, as it returns only a logical value - finds a dependency of some kind, but doesn't go any further. Now depending on where you start and which kinds of relations it looks for (i.e. whether it's a "current table has foreign keys into these tables" or also "these tables have foreign keys into this table") this may serve to find orphans, i.e. tables which aren't a part of the big family of grandparents, cousins and nephews. Which means absolutely nothing, these orphans are there because they were needed.
>
>Any decent SQL client would have a way to retrieve these relationships and even draw diagrams; writing more code to do the same in a way that outputs far less information looks pretty useless to me. Or unfinished... there may have been some idea of traversing the relationship tree and generating some documentation but, again, there are tools out there which already do that.

The code looks very ancient. Possibly the servers those days where not so sophisticated or the coder needs to have it for some reason.