I have a complaints form that has about 30 fields in it.
The first part is the person's information (name, address,
phone, etc). Second is the trip information (drop off
address, time, trip type, etc). Third is the complaint
information (complaint type, summary, etc).

Let's say a customer calls in about two complaints for one
trip (it was late and the driver was rude). The service
rep needs to enter this as two records, but the person's
info and trip info are the same.

So, the rep enters all the information in the first record
for the first complaint. The rep would then click on a
Duplicate Record button. The button would go to a new
record, copy the person's info and trip info from the
previous record, and leaving the complaint info blank for
the rep to fill in manually.

Is there an easy function to do this? I was thinking of
using an append query (db.execute insert), but then I
can't capture the new PK to go to that record.

The only way I came up with is to use the Dim statement,
capture the current field infos, go to a new record, and
insert into the new fields. However, this requires typing
the new and old field names on each line...that's 20
records to do like:
forms!newrecord = forms!oldrecord


Is there anything else i can do?
Ngan

"Ngan Bui" <(E-Mail Removed)> wrote in message
news:034601c37d3b$e1a64aa0$(E-Mail Removed)...
> I have a complaints form that has about 30 fields in it.
> The first part is the person's information (name, address,
> phone, etc). Second is the trip information (drop off
> address, time, trip type, etc). Third is the complaint
> information (complaint type, summary, etc).
>
> Let's say a customer calls in about two complaints for one
> trip (it was late and the driver was rude). The service
> rep needs to enter this as two records, but the person's
> info and trip info are the same.

Have a second table with a one-to-many relationship to the first. Each "header"
record can then have as many complaint entries as you want and you only enter the
header stuff once. Use a form/subform for the data entry.

Actually, this is an exception to the rule. Needing to
duplicate the information only happens about 10% of the
time. Do you still think I should have a second table?

Ngan

>-----Original Message-----
>"Ngan Bui" <(E-Mail Removed)> wrote in message
>news:034601c37d3b$e1a64aa0$(E-Mail Removed)...
>> I have a complaints form that has about 30 fields in it.
>> The first part is the person's information (name,
address,
>> phone, etc). Second is the trip information (drop off
>> address, time, trip type, etc). Third is the complaint
>> information (complaint type, summary, etc).
>>
>> Let's say a customer calls in about two complaints for
one
>> trip (it was late and the driver was rude). The service
>> rep needs to enter this as two records, but the person's
>> info and trip info are the same.
>
>Have a second table with a one-to-many relationship to
the first. Each "header"
>record can then have as many complaint entries as you
want and you only enter the
>header stuff once. Use a form/subform for the data entry.
>
>
>.
>