It seems to me that your description doesn't quite make sense. If you want to create a new blank record, why do you not just create a NEW record instead of duplicating? Perhaps you could have another go at explaining yourself.
Thank you for replying. You make a good point. I will look into creating a new record after setting variables for several key fields from the original. Then I can set the key fields in the new record with those variables and duplicate the related records from the original with the sub-function I already have.
If I duplicate my right shoe, I expect to get a shoe, not a footprint.
sometimes forum people look exactly like my clients, they try to explain their needs in filemaker terms (failing at that, heavily) instead of telling me what they really need, in plain words.
I think I get your point.
What you want is (I think) to duplicate all your record except the primary key that should be different between the records.
Well you can't.
What you should do is:
- Duplicate your record
- Set your primary key field to acquire a new value (you must be sure for this step to not check the "Prohibit value modification")
As example, the primary key usually contains UUID value
Then after duplicate, use: Set Field (primary key ; Get (UUID) )
Thank you all for your replies. I was able to rethink the design and create a script that saves key field contents to variables, creates a new record complete with auto enter options, then set the key fields in the new record from the previously created variables. I was originally thinking in terms of duplicating a record and setting most fields to blank, thus prompting the original wrongheaded question that brought consternation from some. It's all good and I do appreciate all the assistance this forum has offered recently and in the past.