reference:  This has been carried over as a new item from an earlier posting by me at: http://www.lantica.com/Forum2/cgi-bin/yabb/YaBB.pl?board=gen_disc;action=display... , subject = Elements not saving data.
=====================================
Using the following programing as reference:

Quote:


If there are 10 records in the database, then each one has a unique record number, 1-10.  If I add a new record, it will become record number 11.  (Do not actually add the record, just confirm what the value will be).

However, if I delete records, 6-10 first, then I only have 5 records, each with its unique record number 1-5.  If I now add a new record, it will become record number 11.  But I really expect it to become record value = 6.  This should not be happening.

Sesame seems to be working as if these records were never deleted.  The XLR command seems to be looking at deleted records.  Are records actually being deleted, or are they just being tagged internally as deleted?  Is there a process that needs to be done after "deleting" records to have them really fully deleted?

I have confirmed this in two forms in two different databases.

Yes, it does appear to be corrected if I close the Application and then Open it again.    Sounds like an easy fix at your end.....(always easy when its someone else's problem)

I was sure you would see this......aaarrgh!
This is in the application that needed the hot fix for fields added with Field Manager. 

Let me try a few more things.  I will keep copies of existing files in case you want them later.

I will delete all records in DB, make a new DSR from the empty DB, Save as new Application, and try to do this again.

Stay tuned.....

New symptoms......file is on the way to support@lantica.com

Bob,

Your current problem is that the record number continues to increment when pressing F9, even though the record number is no longer blank. I believe that the problem is your conditional. You say:

IF @ISNEW OR @ADD OR @ISBLANK(Record)

Pressing F9 does not change your being in Add mode. @ADD will return True and this programming will run.

I apologize. I see the reference to frmParts in your email now.

No, I don't see the delete problem. I suspect that, while stepping back and forth to check your values, you may have been incrementing them, causing you to get a higher number than you expected.

Also, I recommend using AND instead of OR in this case.
IF @ISNEW AND @ISBLANK(Record)

Deleting records at the end of a stack in Add mode can temporarily trigger @IsNew and may increment your already filled in record number.