Most of the time you get the error 'Cyclic Relation' on SET RELATION when you attempt to set a cyclic relation.
This is a scenario when you DO NOT get an error even if you set a cyclic relation:
-Let's say we have 3 tables: A,B,C, ordered by some index.
-Select A and set relation to ... into B, ... into C

   A
  / \
 B   C

-Select B, and set relation to ... into C

   A
  / \
 B - C

This is a cyclic relation that (V)FP allows you to set without eror. However, you get 'Table is aleady engaged...' when you select A. I see it as a bug.


>It seems that there are occasions when users of my EXEs get the gray "Program Error" box with a message like:
>

>   Target Table is already engaged in a relation
>

>along with choices to Cancel, Ignore, etc.
>
>Now, I have an "ON ERROR" which is supposed to shield the users from such programmer-nonsense, either by attempting to correct the problem, or, more likely, to save some relevant information for me to fix.
>
>First question: Why in the world does the user get this message? In my EXEs, I never want my users to see such balderdash.
>
>Second question: When I run this in my development environment, I get the same message box, with the option to Suspend -- but suspending does not leave at the offending line of code (which, so far, I am unable to discover).
>
>Third (related question): There seem to be a slew of related program errors which give error messages without providing any debugging assistance ... my favorite has to do with a failed DynamicBackColor ... I learn that it has failed, but there is no indication for which column. Is there any hope of getting error messages that provide enough information as to actually learn where the error is occurring?
>
>Thanks.