Dan Waters
dwaters at usinternet.com
Wed May 28 18:56:04 CDT 2008
Hi John, Another example on memo fields. My business process screens typically have a Comments field where any participant can add a comment. For some issues, the Comments field gets a lot of information! In the main screen the Comments field can be read, but not changed. To add more to a comment (once entered it can't be changed), the user pushes a Comments button to open a new screen which has a top half and a bottom half. The bottom half contains the original comment in a locked textbox, and the top half contains an empty unbound textbox. The user enters their new comments into the top half, then pushes a Save Comment button. Their text is added to the bottom of the original comment with a blank line and a line which contains their full name, the date and the time the Save button was pushed. This way anyone who reads the comments knows who made the comment and when. When the Save button is pushed, the original text is concatenated with the new text, and an UPDATE is performed to replace the original content of the table's Comment field with the new content. This keeps the record from being locked while the Comments field is being edited. I originally created this to set up name, date, and time stamping - I wasn't thinking of locking issues at the time. There is another method whereby someone who has authority (a 'manager') can actually edit the Comments field, but it doesn't get used often because who wants to ask their manager to fix their typing? There is also an automated spell check function so misspelling isn't a problem. Maybe THIS will help! ;-) Dan