copy/paste a recordset

[Slez via AccessMonster.com]

What is my best option for enabling users to copy and paste an entire
recordset, but allowing them to change the value of the "one" record in a
series of one-to-many relationships?

For example:
EstimateID in tblEstimate is on the one side of a relationship with records
in tblItem...
which is on the one side of a relationship with records in tblItemDetail.

What I'd like to enable users to do is (maybe via form?):
Select EstimateID "2", then users could enter a new value, such as "5", and
it would generate a complete new set of records associated with EstimateID 5
that matches EstimateID 2.

Why? I have an estimating database, and we often are asked to rebid projects,
and working off a previous estimate is substantially faster that re-entering
the entire project. We want to leave, in the example given, EstimateID 2, in
tact, but the recordset may be almost a 100% match. I hope this all makes
sense.

Any suggestions are appreciated?

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200611/1

[Tom van Stiphout]

On Fri, 17 Nov 2006 16:15:51 GMT, "Slez via AccessMonster.com"
<u23064@uwewrote:

Provide a Copy Estimate button on the Estimate form. The user would
click it when she's on the From-Estimate. Then prompt to enter a new
EstimateID (or have one system-generated), and then you do the work
behind the scenes with parameterized append queries that look back to
this form for their parameters.

-Tom.

>What is my best option for enabling users to copy and paste an entire
recordset, but allowing them to change the value of the "one" record in a
series of one-to-many relationships?

For example:
EstimateID in tblEstimate is on the one side of a relationship with records
in tblItem...
which is on the one side of a relationship with records in tblItemDetail.

What I'd like to enable users to do is (maybe via form?):
Select EstimateID "2", then users could enter a new value, such as "5", and
it would generate a complete new set of records associated with EstimateID 5
that matches EstimateID 2.

Why? I have an estimating database, and we often are asked to rebid projects,
and working off a previous estimate is substantially faster that re-entering
the entire project. We want to leave, in the example given, EstimateID 2, in
tact, but the recordset may be almost a 100% match. I hope this all makes
sense.

Any suggestions are appreciated?