Gustav Brock
Gustav at cactus.dk
Mon Mar 30 10:51:25 CDT 2009
Hi Rocky You are right. I have never used this technique myself. I think it works best for one time only fill-in type forms. For a database type application with repeated new entries it doesn't make much sense. /gustav >>> rockysmolin at bchacc.com 30-03-2009 17:37 >>> Gustav: That does make is stand out better. Thanks. I still think it's an idea of dubious merit but whatever the client wants...that I can't talk them out of. Rocky Smolin Beach Access Software 858-259-4334 www.e-z-mrp.com www.bchacc.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock Sent: Monday, March 30, 2009 8:24 AM To: accessd at databaseadvisors.com Subject: Re: [AccessD] An Interesting question Hi Rocky That depends. The text should be a small sentence that doesn't look like a value. Also, you may add colour easily: @[Blue];"Choose an activity"[Red] This may be useful to distinguish mandatory/required fields from those that optionally may be filled in. /gustav >>> rockysmolin at bchacc.com 30-03-2009 17:10 >>> Gustav: Thanks again. I think the whole idea here of displaying the literal value is not a good one because I did it on a couple of text fields and instead of being blank, which visually tells the user that they don't have a value there, it looks like there has already been a value entered. If you don't read it closely, you could end up with records that need values and those fields and don't have them. Rocky Smolin Beach Access Software 858-259-4334 www.e-z-mrp.com www.bchacc.com