If there's someone from egroup lurking, can you respond to the following: Was there a conscious decision made to not use the Today function for Membership Status? As most people have probably found out, that is the one "FAST FIND FIELD" that is most definitely not fast, being an unstored calculation. For a large-scale database, it takes quite a while to do a find based on Mbr Status. We're doing a customization of ebase, and are considering changing the function to stored by using Today. Since membership status depends only on payments, using Today the status for each payment can be stored in Paymnts, and then the "Fast Find" field in Names can simply be a related field through a relationship that gives the last Dues payment. Indexed and fast. As long as we're aware that this function will be recalced once every day when we open the database, is there any other ebase-specific reasoning we should know about that might dissuade us from taking this route? Thanks much, Matthew Scholtz San Francisco, CA
