B
BJM
Gary,
you wrote...
Am I correct in thinking that the following is the crux of
what you are looking for?....
"The person needs to see proper names but capture the ID
numbers to
the new records. "
The best way to do this for data entry or record lookup is
to use a multi column combobox. You can have the wizard
build it for you or build it yourself. The key here is to
have the ID be the first column and what you want them to
type in to be the second column. If you set the column
width
to "0" for the first column it will be hidden. The wizard
will offer the option to 'Hide the Key column". Make sure
that the bound column is set to 1 and it will now store the
ID even though the user will never see it.
Gary Miller
Sisters, OR
....
Thanks, Gary for your reply. I understand this and have
already put this into practice to create a form based on
the underlying table. What I would *really* like to do is
prevent the data entry clerk from having to use the form
to create 900+ records a week using multilple combo boxes
populated each with dozens of records. It's too much
scrolling to keep a person sane!
Since I gather the attendance data to enter from a report
based on a query, I would like to be able to take the
report's data and "capture" it somehow into the table as
records.
I understand that the report is a print media but is there
anyway to capture what it prints as table data? All fields
in each record are in the report except for the current
week's attendance figure that the teachers enter on the
paper report. (I know, but some of our teachers would be
terrified if we suggested they enter it electronically!)
I hope I have made my needs clearer this time.
Thanks,
BJM
message
..
you wrote...
Am I correct in thinking that the following is the crux of
what you are looking for?....
"The person needs to see proper names but capture the ID
numbers to
the new records. "
The best way to do this for data entry or record lookup is
to use a multi column combobox. You can have the wizard
build it for you or build it yourself. The key here is to
have the ID be the first column and what you want them to
type in to be the second column. If you set the column
width
to "0" for the first column it will be hidden. The wizard
will offer the option to 'Hide the Key column". Make sure
that the bound column is set to 1 and it will now store the
ID even though the user will never see it.
Gary Miller
Sisters, OR
....
Thanks, Gary for your reply. I understand this and have
already put this into practice to create a form based on
the underlying table. What I would *really* like to do is
prevent the data entry clerk from having to use the form
to create 900+ records a week using multilple combo boxes
populated each with dozens of records. It's too much
scrolling to keep a person sane!
Since I gather the attendance data to enter from a report
based on a query, I would like to be able to take the
report's data and "capture" it somehow into the table as
records.
I understand that the report is a print media but is there
anyway to capture what it prints as table data? All fields
in each record are in the report except for the current
week's attendance figure that the teachers enter on the
paper report. (I know, but some of our teachers would be
terrified if we suggested they enter it electronically!)
I hope I have made my needs clearer this time.
Thanks,
BJM
message
I have a report that is handed out weekly to all our
teachers to gather attendance records for the previous
week. This report is built on a query in order to sort and
group records to be entered into an underlying attendance
table.
I also have a form based on the underlying attendance
table. It is cumbersome and hard to manage simply because
of all the many to many relationships that come as a
result of our organization's setup. There is nothing I can
do about that.
What I would like to do is create a form based on the
report that would enter the records directly into the
underlying table.
The real problem is that table records are kept based on
13-character string values for student #, teacher #, etc
which are meaningless to a data entry clerk. The person
needs to see proper names but capture the ID numbers to
the new records.
I'm not sure if all this makes sense, but any suggestions
would be appreciated.
Thanks,
BJM
..