Gina Hoopes
hoopesg at hotmail.com
Mon Oct 24 10:29:52 CDT 2005
Scott and Gustav, I've been reading your comments with interest. I agree with Gustav on the theoretical level because I'm a trainer and I do try to make things as friendly as possible for the end user. However, in this particular case, Scott's solution is still the best. The user has a maximum of 40 hours that s/he can enter. So if I allow them to prepare their own breakdown, usually in an Excel spreadsheet, when they come to the database to enter their final result in my database the rounding would change their total. In this case the user needs to know that the only acceptable increments are quarter hours and prepare their data accordingly. This is a new restriction for them so we need to re-train their process rather than "fix" the data they enter. Thanks for a good discussion with more than one good solution. Gina -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock Sent: Monday, October 24, 2005 10:06 AM To: accessd at databaseadvisors.com Subject: Re: [AccessD] Quarter hour increments Hi Scott First, you forget the original questioner, Gina. I don't think she has a business layer. If so, the frontend is where to put sophisticated business rules as only simple validation is possible at the table level. Still, if a business layer should be present, I agree that would be where to put it.