> Paul's answer is technically correct, but practically disastrous. Setting a trigger to be inactive is a system-wide event and will stop other transactions on other connections from logging their changes. <

The Stored Procedure would normally be run at a time when other users would be inactive, however, I agree that it's a gamble, and the risk is too great. Fortunately, I was able to refine my Select query so as to minimize the impact on logging (a lot). The biggest problem was created by re-computing people's age each day. I eliminate that need by using a Calculated Field in the application, so the problem seems to be solved.

Thanks to everyone for the help.