>>Here is an example...
>>

>>IF _triggerlevel=1
>>   DO riend WITH .F.
>>ENDIF at the end of the highest trigger level
>>

>>
>>There is some text after the ENDIF, I made the change you suggested, and no error was detected... and there are neither #DEFINE nor #INCLUDE in the stored procedures..
>
>First of all, that is standard RI-code. The previous developer didn't write it - it was generated automatically by the RI-builder (the previous developer must have defined some referential integrity).
>
>Second, while this is not exactly standard, it is legal: any text after ENDIF is ignored, so you can put your comments there, with or without "&&".
>
>I would recommend using "&&" for your own code - for a start, you will get correct syntax highlighting. But it isn't worth-while to do any changes to the RI-code; next time you generate the referential integrity, it will be overwritten anyway.

Thanks a lot.. I didn't know the text after ENDIF was ignored.. Can you give me some recomendations on how to learn more about stored procedures? some kind of step by step?