N
Nicholas Scarpinato
Hello. I'm working on a project here at work and unfortunately I'm stuck with
using Access 97 to do it, which from what I understand means I don't have
access to using a recordset as a form/subform's RecordSource object. What I'm
trying to accomplish is a subform that has add/remove buttons which, when
clicked, insert a new record after the current one, or remove the current
one. This is for a data entry screen, so it would all be blank records that
the user fills in and then commits to a table. The user can enter up to 15
different line items for each checklist (the database is a process audit
checklist generation/audit results storage database). The reason for this
modular approach is simply for ease of use for the people using the database;
I have a current version of this same entry screen that is already working,
but it's cumbersome and somewhat confusing (and as such, fits perfectly in
line with everything else in this company... which is what I'm trying to get
away from).
My first guess is that doing this will require a temporary table which
stores the information entered on the form. Then, using vba, write some code
to update the records based on if a new record is added/deleted (although I'm
not sure how to re-index it from a continuous form; I haven't figured out how
to determine the current record). Then requery the form's recordsource, which
would be the temporary table. However, this seems rather... tedious, to say
the least. Is there another way to do this, or should I just let this idea
fall by the wayside altogether...?
using Access 97 to do it, which from what I understand means I don't have
access to using a recordset as a form/subform's RecordSource object. What I'm
trying to accomplish is a subform that has add/remove buttons which, when
clicked, insert a new record after the current one, or remove the current
one. This is for a data entry screen, so it would all be blank records that
the user fills in and then commits to a table. The user can enter up to 15
different line items for each checklist (the database is a process audit
checklist generation/audit results storage database). The reason for this
modular approach is simply for ease of use for the people using the database;
I have a current version of this same entry screen that is already working,
but it's cumbersome and somewhat confusing (and as such, fits perfectly in
line with everything else in this company... which is what I'm trying to get
away from).
My first guess is that doing this will require a temporary table which
stores the information entered on the form. Then, using vba, write some code
to update the records based on if a new record is added/deleted (although I'm
not sure how to re-index it from a continuous form; I haven't figured out how
to determine the current record). Then requery the form's recordsource, which
would be the temporary table. However, this seems rather... tedious, to say
the least. Is there another way to do this, or should I just let this idea
fall by the wayside altogether...?