>>>>>When I run the View Designer I get the following message when I try to quit the designed:
>>>>>
>>>>>SQL Column "Auth_code" is not found. There is an auth_code field in each of the tables that makes reference to them. I picked them with the designer. Here is the SQL code when viewed:
>>>>>
>>>>>SELECT *;
>>>>> FROM calllink!faxque INNER JOIN calllink!schedule;
>>>>> INNER JOIN calllink!pending;
>>>>> INNER JOIN calllink!assigned;
>>>>> INNER JOIN calllink!account ;
>>>>> ON Assigned.actnum = Account.actnum ;
>>>>> ON Pending.actnum = Assigned.toll ;
>>>>> ON Faxque.audit_num = Pending.audit_num ;
>>>>> ON Faxque.audit_num = Schedule.audit_num
>>>>>
>>>>>What is going on?
>>>>>
>>>>>Ed
>>>>
>>>>
>>>>I made a Typo. The error is: "Audit_num" is not found.
>>>>
>>>>PS: How do you delete a thread when you discover an error afer you send it?
>>>>
>>>>Ed
>>>
>>>Ed, the answer to the second question is "You don't" You just leave your mistake for everyone to see. It keeps us humble. (As if FoxPro didn't do a good enough job.)
>>>
>>>As for the first question, was the typo in your code, so it works now or in the message so you still have a problem? The SQL looks okay to me....
>>>
>>>Barbara
>>
>>Hi Barbara.
>>
>>No, the typo was the error message that I wrote here. I't beginning to look like a corruption in one of my tables though. Gee, that's never hapened before. If I "COPY STRUCTURE" to another file and try to use it, the problem still persists, but if I create a new table from scratch, copy just the data and use it, it seems to work.
>>
>>Ed
>
>Ed, try Validating your database
>
>OPEN DATA CALLLINK exclusive
>validate data recover
>
>See if you have any problems with the DBC. It's easy to make a structure change or add an index to a table when the DBC isn't open, and then your headers get mixed up. This may be why a new table corrected the problem. It's a good idea to do this occasionally if you're making structure changes.
>
>HTH
>Barbara

Thanks Barbara, that's good to know