Try using NotifyForm to prevent the form from advancing. Also, use Writeln to make sure that your conditions are correct.

Hi -

I'm back and trying to get this worked out.

Attn: Bob (but Mark and everyone else is welcome to read it too (lol)

Now that you mention it, I vaguely remember using F8 in Q&A; however, it may not have been in this type of situation.  In any event, it has been so long since I've used Q&A that - unless I remember programming "format" or "structure" (that makes programming in Sesame easier for me, without having to look up the correct syntax in Sesame) - then having used it in Q&A is simply of no value to me (nor do I care - lol). The bottom line is that I am reading the Sesame programming documentation and I am not able to accomplish what I want (and I need to).

Attn: Mark (but Bob and everyone else is welcome to read it too (lol)

I was not familiar with the Notifyform option and that has helped me move a little closer.  The form does not advance unless the conditons are satified. First, here is the code I am currently working with and it is back in the "on form exit" event.

If @isblank(first name) and not status = "Incomplete"
then
{
notifyform(1)
@msgbox("You must either enter something in the first name field","or enter 'incomplete' in the status field","")
throwfocus(Status)
}

if status = "Incomplete" or not @isblank(first name)
then
notifyform(0)
 

If either condition exists, the form behaves exactly as I want it to and I can advance to the next record.

If, however, either condition is not satisfied, I do get the appropriate message and the form does not advance until either one of the conditions are satisfied (which is precisely what I want); however:

1) Throw focus does not take me back to the status field.  

2) What advantage is there to using writeln to tell me the conditions are met (since I prefer not to have extraneous information appear on the form unless it is necessary).

a)  If the condition is not satisfied, I get my notice and the opportunity to correct it. Once it is correct, I am then able to advance to the next form.

b)  If the condition is satisfied, I simply advance to the next form, which is what I want to do.

Once again, if I am overlooking something I would like to learn.  The bottom line (in my mind) is that if something is done correctly, I don't need confirmation of that fact. It is only when something is not done correctly that I need to be alerted.

Eagerly looking forward to the "solution" so that I can continue with other programming.

Thanks!

Indeed, I meant that in particular. The Writeln command will popup a separate window that can be written into pretty much freely. It is very useful for debugging programming in that it does not affect your form, and once the programming is okay, you can remove the writeln statement easily.

Quote:


If you need to be certain, ask Ray to test it in the the latest build they have.

Quote:

Actually Ray is off visiting. He'll be back Monday.
Quote:

One of the 1.1.3 Alpha testers reports that there was a bug associated with ThrowFocus and On Form Exit events. He also confirms that it has been fixed in 1.1.3.
Quote:

We have a go ahead from alpha and from Lantica marketing to start packing it up. But it really isn't up to development (or support) to set the final date.
Quote:

Version 1.2? Do you mean 2.0?

As far as I know there are no plans for a 1.2.

2.0 Runtime has pretty much reached critical mass and should be going into a test cycle soon. There are quite a few SDesigner features we would like to add before it gets locked down. After both developments are locked, both will have to go through testing and docs, then marketing will do its voodoo on price and product position, and make decisions about 1.x support and features.