There is a reason to break a relation and that is not an error. From documentation:
"...if you change the Order property at run time of a cursor that is involved in a one-to-many relationship, the one-to-many relationship is broken."
Cetin


>Cetin --
>
>I had guessed that I could rummage around in the code -- my question (which you answered, indirectly), was whether VFP left any hint as to where the relation was broken. I assume that there must be reasons to break a relation, so that when you do so unintentionally your program should not fail immediately.
>
>Sigh. `
>
>>I don't know, need to reproduce to be able to check for a workaround.
>>I would check which tables I set relation to and then search for code closing them in code. If it's a cursor then check for code "select ..." code selecting into same cursor name. Also check for "use" code.
>>
>>PS: You're saying when closing form. Then check code in 'closing' routines.
>>Cetin
>>
>>
>>>So, I have no way of knowing where the relation is broken? There's just a not-so-helpful message which flashes, and execution continues?
>>>
>>>>>I'm getting "Relation Broken" when closing a form, followed by an error on a line that's trying to do

Select someCursor

>>>>>Am I to understand that the error occurred on the line where the relation was broken, or could the relation just have been broker earlier?
>>>>>
>>>>>TIA,
>>>>
>>>>As I see it, relation is already broken and someCursor (which was part of the relation) was closed before that line.
>>>>Cetin