We’ve been using TIE since version 1.6 and so we started off running all of our direct marketing activity using smart fields. We quickly ran into performance issues and SQL server limits which were addresses in version 1.71 with balanced smart fields. We are now on version 1.8 which has introduced selections. We have not started using these extensively yet mainly because I am unsure how they will work for more complex selections. For example, we may want to do a selection to select people who have made a gift within 2 weeks of an action. I cannot find a way to compare dates like this. Also, we often end up with segmentations with many different segments. We may be mailing committed givers, cash donors, major donors, etc and then splitting all of these groups by whether they are getting the email or mail version, then by the regency of their last gift, etc. You can very quickly end up with a lot of different segments. I can see that there are a couple of ways of doing this: [b]A: Create one segment for each selection.[/b] Pros:[list][*]Don’t need to worry about dependencies [*]Keeps number of selections small[/list]Cons:[list][*]If you need to change the criteria for a cash donor, you need to change it in multiple places. [*]Performance is possibly slower with this method[/list] [b]B: Create segments for each group and then combine these to get your final segments[/b] Pros:[list][*]Definitions are not repeated, therefore changing the criteria for a cash donor for example changes it everywhere it is used [*]Faster[/list]Cons:[list][*]Having dependant selections means that you need to be aware of the dependencies and refresh them manually in the correct order[/list] Do you work in another way? How do you get around these limitations? Am I missing something!?? -- Stephen Newberry e: [Email Removed] [i]--- Edited at 4/19/2007 5:47:40 AM by Stephen Newberry[/i]