How to repeat fields entered in a subform

[CuriousGeo]

I have a form (based on ArtistSong) and a subform tied to the ArtistSongID. This subform is a set of 11 variable attributes of that Artist & Song combination. Also, there can be multiple records in that subform, all associated with the Artist & Song.

The user would like, when he makes an initial entry of 11 attributes, to go ahead and repeat that particular combination in the next New Record.

Is this possible, is it advisable to do such a thing? This is beyond my scope of knowledge for Access db building.

Here are screen shots so you can understand what I am talking about.

Thanks for any input!

 

[CuriousGeo]

As a side note, before someone asks "Why do you want duplicate records?" ...

the user just wants easier data entry, the majority of the fields would stay the same, but 1, 2 or more fields will be changed by the user, so the new record really won't be a duplicate after the user has made his minimal changes.

 

[JHB]

Can't you use/set the default value for the control, when a field is getting updated, (in the After_Update event)?

 

[CuriousGeo]

Just wanted to update this thread in case it will help anyone with a similar situation. I have found the solution this question. When entering a records in a form, I wanted fields to be duplicated for the next new record and I found the solution using DMAX and DLOOKUP. I found a tutorial on youtube from a guy named Richard Rost, 599CD Computer Training: Copy Last Entered Record

 

[2ndLife]

CuriousGeo, thank you for that video from Richard Rost. I've been watching his videos off and on for about a year now and he's taught me so much. It helped resolve my issue, as usual.

 

[Pat Hartman]

"Last" is a nebulous value when you are talking about relational databases. If you want a "copy" function, it is more flexible to put the copy button on the detail form and use the concept of "this record". Your append query can use the PK of "this record" to select the fields you want to copy and leave the fields the user needs to change empty (null).

But, you might want to review your design. Attributes that don't change belong in the parent record. So, maybe your problem goes away if you properly normalize the tables.