>>I am attempting to create relationships in the DE of one of my reports, and seem to be getting inconsistent behavior. Specifically, it won't let me drag a field from the parent table to the matching field in the child table, only vice-versa. There are indexes on all of the appropriate fields, and the kicker is- this relationship was there before! I believe that this is a glitch in VFP because I have run in to the same problem on other reports and been able to solve it by restarting VFP, and then it will allow me to create the relationship. At first I thought that I was just confusing which types of realtionships I am allowed to do; field to field, field to index, index to index, or index to field, but I double checked, and the relationship I had created before was now prohibited. What gives? Is there a setting I am overlooking or is this really a glitch? Thanks for any insight.
>>
>>Erik
>
>Hi Erik,
>
>1. Unload and re-load VFP just to make sure you don't have any weird stuff going on in the background. I've found that occasionally a file/form will turn read-only because of something in a non-closed datasession (Errors during development? Not ME!)
>
>2. Try setting your relations programmatically in the LOAD or INIT methods. I always do this to prevent the problems you're having. Sometimes they just WOULDN'T set correctly visually. It may have to do with the order the cursors are being loaded. For example, did you delete a cursor and then add it again?
>
>HTH
>Barbara

I finally solved the problem, I'm just not sure how. I deleted all of the cursors in the DE, and then created them and the relationships from scratch and it worked. I think that the order in which the relationships were created was relevant. Well, even though I don't know what caused the difficulty, I know how to tryand cope next time. Thanks for your help.

Erik