I’ve been trying to mass update using the following code to copy Stock# data from the Main form to a new record in the Subform called Details. There’s actually five other data elements that are copied along with Stock# at the same time,  I didn’t think you’d want to see the code for all of them.

var vstk1 as string
var nn as string

If @FormFieldValue("Details", "Stock#", 0) <> "" Then
                 {
                       nn = @FormNewRecord("Details")
                 }
                 Else
                 {
                       nn = 1
                 }
           
     vstk1 = @formfieldvalue("Main","Stock#",0)

     FormFieldValue("Details", "StockNo", nn, vstk1)


There is already 1 row of information in the subform. When I run mass update a window pops up and says; “Executing a mass update on 1 record.”.  It copies the information correctly but it randomly (no pattern that I can find) creates two entries of the same thing instead of just one.  If there are two rows of data in the subform, the popup says; “Executing a mass update on 2 records.” When I press continue it again copies the information correctly but this time it sometimes creates two or four entries of the same thing instead of just one.

Have I missed a vital part of the code to make it copy only one row of data instead of duplicates?

Also, I’ve had to use a macro to mass update all records, there’s 2600 of them. Is there code available that will do this instead?

Any help would be appreciated.

You are correct. I originally attempted to run this from the main form but I couldn’t get it to place the data in a new record on the subform unless I ran it from the subform. I just tested it again, running it from the main form instead of the subform. It copies the data over the existing first row of data on the subform. What do I need to change so that the data will be placed into a new record on the subform?

Sesame Personal 2.0.6

That did the trick!

Thanks very much for your help.

tcgeo wrote on Jun 9^th, 2008 at 3:27pm:

In 2.x, if @FormResultSetTotal returns zero, then there are no existing subrecords and the first row should be used since it is a new blank record waiting for you to type something.  Otherwise, there are already existing records and we should make a new one instead of using the first row.

This is slightly different from 1.x and some of the examples may still reflect the older behavior.