Thanks Chris for responding
>
>My first bit of advice would have been 'Ensure the table being joined twice has two aliases', but the SQL appears to have that. So, I've only got two SWAGs left: Ensure that the fieldnames in the result set have unique names, and try rewriting the SQL in sequential order, it might make more sense.
>
>Chris.

I have got this generated automatically by the VFP View Designer. The sequential order should have been maintained as I first saved the view with the first join and got it working on my form. Then reopened it and added the same table again in the View and joined this another one. I tried to switch the joins into 2 places in seq. order i think was valid but then the VFP view designer said that the index is corrupted and that I should rebuild it for this view???

Any suggestions? Any way you feel the view SQL should be I can cut-paste (I am not much of a coder) into the View using View Editor which will allow me to do it.

But one thing I had noticed is that the VFP View Designer when I added the Master table the first time around put up 2 joins on it's own, would it have given me 2 diff. record pointer for my form?

Is this possible, have you done such an SQL/View in the past?