Actually this converted 6.5++ report was originally based on a view with alias names. I converted it and changed the driving table to a real table, however the problem fields for me were some lookup variables. Replacing the object did the trick so I am happy. I don't think there is any bug to worry about with this. Thanx for the tip on it.
Thom
At 09:40 AM 07/09/2003 -0400, you wrote:
At 12:51 AM 7/9/2003 -0400, Thom Cimicato wrote:I had this exact same thing happen to me today in fact. Here is what I did that worked.
Simply delete the field, then replace it with the exact same object. I don't know why it worked or wasn't working in the first place but it fixed the problem and it was easy.
Dear Thom and David;
A little anomaly that I found in certain reports is that if the report is based on a view, make
sure to use column aliases or the T1.column names will cause a glitch in the report
where every time you add or alter a field, it or another will disappear.
This may or may not be relevant in your case, but I thought that I'd throw it out there.
Check it out.
Mike
Thomas J Cimicato President Integrated Check Technologies Collect-A-Check, Inc. ------------------------------------------------------------ Bus:800.338.0676 Mailto:[EMAIL PROTECTED] www.ICheckTech.com
