Hi Doug,
I've tried what you suggest and it works but my problem is that the fields in question are pretty major, one of the three fields is a candidate key in almost every table, so the code would be pretty long to replace about 100 occurrences and I'm afraid I might miss one table. Can you think of a more 'global' method to catch all occurrences? Also on the subject, I have alot of reports that are driven by SQL statements. Some of the SQL statements and/or views are so long I had to code aliases to shorten the SQL statement (ie if the table was called customer my SQL includes 'FROM customer cu' so I refer to it in the body as cu.xxx. The problem is that the filters that are returned do not 'filter' the SQL because of the alias change. Is there some way to override this so when a customer sets a filter, it will get used because of persistent relationships?
TIA,
Sandi Cassidy.
>You can put it in your own code sometime after the instantiation of SFQuery. Reference the oFieldCollection object of the SFQuery object. For example:
loField = oQuery.oFieldCollection.Item('customer.company')
>loField.cFieldExpr = whateverDoug
