Results 1 to 4 of 4

Thread: Access (2000)

  1. #1
    New Lounger
    Join Date
    Mar 2002
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Access (2000)

    I have created a database to input 5000 comments. Is there a way to enter the same information twice, such as an address to check for quality/typos? My manager thought there was a way to do this so that the system would automatically check for quality and we wouldn't have to have someone proof all the information.

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Access (2000)

    This is sometimes called data verification and there have been some threads discussing entering duplicate data for this purpose. It's an old concept from the days when data entry was done all day long at terminals where you couldn't really see what you had entered and were required to key as fast as was physically possible. In my opinion, it's a waste of time because entering data incorrectly twice doesn't make it correct. <img src=/S/shrug.gif border=0 alt=shrug width=39 height=15>
    Charlotte

  3. #3
    Lounger
    Join Date
    Jan 2001
    Posts
    43
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Access (2000)

    Two answers: 1 As in Excel, ctrlC copies the info from the same field in the previous record.
    2.Helen Feddema I think wrote about this and suggested using the tag property of a control , maybe that was only for a single field. Have a look under Access Archon on helenfeddema.com
    Hope it helps
    Mike Trotter

  4. #4
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Access (2000)

    You could certainly use the AfterUpdate event of a control to copy its value into the tag of that control, but that would require entering a record twice at the time, not having someone go back later and reenter the data as a verification. You could also use the BeforeUpdate event of a control to test the value entered against the OldValue of the bound control and only move to the next control if they matched, which could be done at a later time, but that would require some intelligence in the interface to know that you were doing verification rather than editing the record.

    Neither method gets aound the problem that a value could be entered incorrectly twice or that the second value entered may be the one that's wrong.
    Charlotte

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •