Newbies Runsible Posted July 22, 2005 Newbies Posted July 22, 2005 I want to create say 200 duplicate records at once, with consecutive serial numbers. I'm ok with the serial no. side of it but not the script to limit the creation of records to a set number. Appreciate any assistance.
aaa Posted July 22, 2005 Posted July 22, 2005 If i understand you: Loop Duplicate record request Endloop Press Esc when you want to stop creating.
Lee Smith Posted July 22, 2005 Posted July 22, 2005 aaa has suggested one way, I'm not sure I can stop a loop in a timely manner with escape. I would create a number field "Counter" and use a script like: Set Field [ Counter; 0 ] Loop Duplicate Record/Request Set Field [ Counter; Counter + 1 ] Exit Loop If [ Counter = 200 ] End Loop HTH Lee
Søren Dyhr Posted July 22, 2005 Posted July 22, 2005 (edited) Edited July 22, 2005 by Guest Sorry I misread the script
Ender Posted July 22, 2005 Posted July 22, 2005 Loop Duplicate record request Endloop Press Esc when you want to stop creating. Hee, hee! Thanks for the laugh, aaa!
-Queue- Posted July 22, 2005 Posted July 22, 2005 (edited) Another option Freeze Window Show All Records Omit Record Show Omitted Loop Exit Loop If [Get(FoundCount) = 1] Go to Record/Request/Page [Last] Omit Record End Loop Loop Duplicate Record/Request Exit Loop If [Get(RecordNumber) = 201] End Loop Edited July 23, 2005 by Guest Added missing End Loop step
Søren Dyhr Posted July 23, 2005 Posted July 23, 2005 Hi JT I understand what you aiming at but, if you take a closer look at the steps ...will you ask yourself: When will you ever reach the inner loop??? --sd
-Queue- Posted July 23, 2005 Posted July 23, 2005 Thanks, Soren. I had inadvertantly omitted the End Loop step for the first loop.
-Queue- Posted July 25, 2005 Posted July 25, 2005 In a multi-user environment, Show All Records Omit Record Show Omitted could easily show 2 or more records; the more people concurrently using the solution, the more likely it will occur. If 2 people create/commit a new record in between the time that Omit Record and Show Omitted steps are performed, then Show Omitted could display 3 records. It is a rare occurrence, but if used in a multi-user solution, it is safer to use the loop or a GTRR self-related ID step when it is crucial to have a single record on which to operate.
Recommended Posts
This topic is 7064 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now