How are you stopping them in "add mode" (in Q&A or not)?

For The Cow:  This is not a problem in Q&A becasue when in Search/Update, pressing F10 send message that No More Records Exist.

For Carl Underwood:  What you provided almost workdedd but i had to make some changes
You gave me this:
If @Update {
If @FormResultSetCurrentPosition(sThisFormName) = @FormResultSetTotal(sThisFormName)
           FormNotifyForm(sThisFormName, 2)
     Else
           FormNotifyForm(sThisFormName, -2)
     }
}

When I used that I kept getting a message the program did not compile when i tried to  open a form.  But when I did Test in Program Editor there was no errors.  I could not find FromNotifyForm in the manuals, but did find an example on page 193 of Programming Gguide.

The first thing that i found out was that i had to put quotes around the form name to meake it work.  And then I used NotifyForm like the sample showed. This is what I ended up with
If@Update {
If @FormResultSetCurrentPosition("sThisFormName") = @FormResultSetTotal("sThisFormName")
           NotifyForm(2)
     Else
           NotifyForm(-2)
     }

But now it is working but where do i find FormNotifyForm in the manuals?  Is this a special funciton that i need to make to use with this?  I am using subforms so i put the same programming in FormEntry sections on top form and the subform.  butt you said there would be troubles unless is used the programming that i cannot find.  I don't want to have problems but the message about not comiling is gone away now and pressing F10 does not go to a new record to be added.  That is good so far.  Also now when I press F10 in updateing mode, the record numbers on top of window flash count but come back to last record.  Is that flashing the trouble you warned about?

Quote:


@FormNotifyForm(formName as string) as int
FormNotifyForm(formName as string, flag as int)
@FormIsNotifyForm(formName as string, flag as int) as int

They are all added in Sesame Version 1.1.3 and you are not likely to find in version 1.1 programming manual.

https://www.lantica.com/Support/sesame_change_log.html

Please view the above Change Log.

Bharat Naik

This is the code that I have been using.   Similar to Carl's but does not use static variable.
Thic can be pasted into any form, and you only need to modify the value of vFormName

var vFormName As String

//Set the name of the form on the next line
vFormName = "frmPhoneBook"

If @Update Then {
	If @FormResultSetCurrentPosition(vFormName) = @FormResultSetTotal(vFormName) Then {
		FormNotifyForm(vFormName, 2)
		} Else {
		FormNotifyForm(vFormName, -2)
		}
	}
 

Note that I have a naming convention that starts all form names with "frm".  But that's another issue.

obfusc88 wrote on May 31^st, 2007 at 3:17am:

Because, you may want to add a new subrecord to the subform while updating a main record.

Quote:


How is a "new but committed" record different from an "old" record?  I generally think of a record as "new" when it has not been committed, but once committed it's "old" (in terms of how a user would access it).

Not to disagree too strongly with Ray (none of us can afford to do that), but that is not really what I intended. When I said "new but committed", I intended a record that the user had committed as part of their current session - a record created in add mode or "extend mode" that has been committed, but was created in this session by this user.