Razzak and Karen,
You got me on the right path. Went to an older working copy of the
report from 3 months ago. Looked at the old view and the current problem
view. I had changed one letter in three column names to stay more
consistent with a naming system that just developed. Makes much easier
reading to me. The name changes were great for other reports, except I
forgot to adjust this one report, so I basically adapted Karen's idea.
Inserted the old names into the current table and up pops the trouble
report in designer. Changed the report fields to the correct names,
moved the data to the new columns, deleted the trouble columns, and it
now runs like it should. Took maybe 30 minutes. The other reports all
work. Than you for the brain kick.
Tom Frederick
[email protected] wrote:
Tom: This probably isn't what happened to you, but just a warning
because I had a 7.6 report give me the same error, but it was my fault.
I was working with a view (permanent) that someone else had defined
long ago. I can't stand views that use T_1 and T_2, etc... Makes
the column definition really hard to read with all those underlines.
So I changed the view definition to use just T1 and T2. Broke my
reports because the saved report definition used the underlines!
Karen
I have a report that has always worked, but it has not been used for
several months. Now, the error message ‘Column XRepPayee not found in
T1 (2368)’ pops up at both design and run and the form will not open.
The column is in the table and view, spelled correctly. Is there some
other way for the designer to open the report so I can edit it? Tried
copying the report to use a blank form table, but it still requires
this column. I can get a copy from an older backup database, but I
would rather fix/understand what happened here. Just reloaded the
database several weeks ago using the procedure Razzak has recommended
many times.
Tom Frederick
Elm City Center
1314 W Walnut
Jacksonville, IL 62650
Off - 217-245-9504
Fax - 217-245-2350
Email - [email protected]
