I do this in a report to find missing check numbers in a checkbook application. But, you can set it up faster in a Mass Update. Here's how:

1. Sort your records in ascending order on the field you want to check.
2. Place this in the Global Code event of the Mass Update spec:

stat sPrevNo as int
stat sCounter as int
stat sList as string 

3. Place this in any other Mass Update event:

var vMissing as int

sCounter += 1

If sCounter > 1
{
	If @TN(Check No) > (sPrevNo + 1)
	{
		vMissing = (@TN(Check No) - sPrevNo) - 1
		sList += "There's " + vMissing + " number(s) missing, starting with " + @Str(sPrevNo + 1) + @NL()
	}
	Else If @TN(Check No) = sPrevNo
		sList += @Str(sPrevNo) + " is a duplicate!" + @NL()
}

If sCounter = @ResultSetTotal()
	WriteLn(sList)

// Create a delayed copy of Check No to compare with next record.
sPrevNo = @TN(Check No) 

You will need to replace "Check No" with the name of the element that contains the numbers you want to check. BTW, I enclosed Check No inside of @TN() because, in my app, that element is bound to a TEXT field. If the element you are checking is bound to a NUMBER field, you can remove the @TN()'s, but it wouldn't hurt to leave them in there in any case.

That's it. Just run the Mass Update, and if there are any duplicates or missing numbers the slate (WriteLn window) will display them when the update is finished.

Good luck!

Thank you.   It was just what I needed.  Worked perfectly.

Carl This is absolutly  marvelous , thanks.

I want the same Techník to determine whether  Form A involves the same number in the form B or NOT!
How kan i do That?

Thanks.

Quote:


I'm not sure I understand you. Do you mean that you just want to know if two databases contain the same numbers?

Try this Mass Update. Of course, you will need to modify the parameters in @XListValues as required to fit your needs.

Make sure you run it on a single record, by using "Max 1" or "Min 1" in the search spec.

var vA as string
var vB as string

vA = @XListValues(@Fn, "Checkbook!Check No")
vB = @XListValues(@Fn, "Checkbook Transactions!Check No")

WriteLn(@DifferenceStringArray(vA, vB)) 

This code will produce a list of values that appear in one of the databases, but not the other. Here's an example of what it might show in the slate window:
20776;20777;20778;20779;21229

Otherwise, if there are no differences, the slate will be blank.

Are you sure the slate is closing? Sometimes it will simply end up behind the main Sesame window. In any case, I think this may solve the problem:

// Close and open the slate to make it display on top of the Sesame window.
CloseSlate()
OpenSlate() 

It won't hurt to use CloseSlate() if the it's already closed. But, if it's not actually closed, and simply behind another window, you need to close it and re-open it to make it come to the forefront. Just using OpenSlate() will not bring it to the front, if it were already open.

Otherwise, if it really is closing without you asking it to, maybe you should send it in to support to have them see what is happening.