Hi Sandi.

> 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?

Unfortunately, I don't have a good answer for this.

> 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?

That would take a lot of reengineering of the code that creates the SQL SELECT statement, I'm afraid.

Doug