Results 1 to 3 of 3
  1. #1

    Automating Data Entry (Accss 97, SR1)



  2. #2
    Super Moderator
    Join Date
    Aug 2001
    Evergreen, CO, USA
    Thanked 65 Times in 64 Posts

    Re: Automating Data Entry (Accss 97, SR1)

    If your database ends up being as complex as your prose it will be a dilly! <img src=/S/hairout.gif border=0 alt=hairout width=31 height=23>

    A couple of suggestions that may/should save you a bunch of keystrokes. One quick way of copying data from the previous record to the current record is a single keystroke (well it involves two fingers) CTRL-' - that works well where you can't set a default, but several consecutive records have the same data. And it works well in both table/query views and in forms.

    The second feature of use is setting default values. That lets you specify a default value at the field level when you create or modify a table. You can also set defaults for forms - each "control" on a form has a default value if it is bound to a field. These default things can also be variables such as the current date and time or the name of the current user, or they can be calculated using information from other fields.

    Finally, your structure suggests that a subform might be useful since you will have one to many relationships, and subforms will automatically populate the pointer fields that are used to link the many records to a single master record. Hope you find this useful.

  3. #3

    Re: Automating Data Entry (Accss 97, SR1)

    Thanks, Wendell:

    I'd been using < Ctrl + apostrophe > in the Datasheet View of my form while I waited to hear from this forum. I entered the class's "Constant" data in its first record, and then I switched to Form View to enter all the class's "Variable" data. When I knew the number of the last record for the class I returned to the form's Datasheet View and I used the keyboard technique to duplicate all that class's "Constant" data in each relevant field. (I was also delighted to watch this method work in the more formatted context of Form View. I thought that was pretty impressive. It' 's a veritable "ditto mark" when it's used in the Datasheet column, but when it operates across a formatted page it's much more impressive.)

    That technique is much better than nothing, but it looks like Subforms will be the best means of automating this process.

    Thanks for your guidance.

    Jeff Hook

    (PS: I've noticed that "Access People" are THINKERS, so I didn't think my "careful" prose would be very much of a challenge... It looks like we both survived my first attempt at construction of an Access database. I wasn't so sure I'd make it.)

Posting Permissions

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