I have noticed this behaviour, also. If the underlying table definition is changed, at the very least, I need to remove the tiers and then add them again. On occasion I have had to remove a field and put it back on again. This usually happened when I modified the underlying view that the lookup variable was accessing, even if the column list remained the same. This behaviour is evident in DOS and WIN versions. I am running 1.866 in both.
[EMAIL PROTECTED] (Thom Cimicato) wrote: >Mike, > >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 __________________________________________________________________ McAfee VirusScan Online from the Netscape Network. Comprehensive protection for your entire computer. Get your free trial today! http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397 Get AOL Instant Messenger 5.1 free of charge. Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455
