Search results

"Thank You" to all that have suggested lines to take . . . . . I have had to leave this particular problem for a short while as I have been asked to "sort ouT" a "Book of Remembrance" for church. (In Access/Db terms it is just a little bit more than a basic address book ~ one form, Two Reoprts...

Thank you Pat. I will give that some thought. Right now, I cannot understand how copying a VALID record can cause its "pasting" to produce a "dirty" anything ~ If I manually carry out the steps whilst working directly on the table (Shrieks of Horror!) the steps work OK . . . . . . Select...

Thank you again. Can you think of a reason why the "Duplicate Record" evolution generates a new record as well as actually duplicating the required one? The Unwanted record contains all of the default data just as if a new blank record had been generated. Thank you again

Blast.! The solution I thought I had found now, NO LONGER works (Sorry to all concerned). Both Macro and Code versions produce an unwanted "blank" record. I will take Pat's advice and restructure my tables because that will address (!) the actual issue I am trying to correct. I do not have...

Thank you for that gentlest reminder of RDB basics ;-) In my defence I did say "I suppose I could have used a variation on the “Clients / Orders” design." I was so pleased with getting all the other routine inputs based upon related tables (and combo boxes) that I quite failed to realise...

I think that this works a little better (it avoids the generation of "blank" records) by selecting where the "copied" record is pasted (Not "PasteAppended"!): DoCmd.RunCommand acCmdSelectRecord DoCmd.RunCommand acCmdCopy DoCmd.RunCommand acCmdRecordsGoToNew DoCmd.RunCommand acCmdSelectRecord...

Thank you for that welcome. OK. I will try to do start a new thread as suggested I have sorted the problem (to my satisfaction) but my suggestion may not win the approval of those that actually know how to write "simple" code! Sid

Thank you very much indeed ~ That has the great advantage of simplicity and got me out of a (self dug) hole. What also seems to happen is that a new (blank) record is created (simple to find and to delete but a nuisance). Is there a way to avoid this just as easily? Apparently (I have yet to...