Quote:


It is that way very much on purpose. The clear is simply there to allow you to temporarily disable all of the mass update. This is especially important in that it allows you to run parts of a mass update without running all of a mass update - very handy during debug, or if you have many different mass update programs (each attached to a differen LE) and you use them individually.

Quote:


Please describe - I am not sure what you mean by "sensitive". I would like to add the ability to search and search/replace across LEs and events.

Quote:


Steve,

It's easy to reproduce on any form. That's how it works. When you close the Program Editor, any element with a Mass Update program typed in it gets the P reset. Clear turns off the P, but does not delete your programming. It's still there, which is why the P comes back.

We agree that it would be nice in all the Program Editors had a Clear All Programming choice that would wipe all the programming. It's on our list. Meanwhile, try saving a blank Mass Update spec. When you want to clear all your Mass Update programming, load that Spec.

Incidentally, there is no real reason to type your Mass Update into different elements. That is mainly there for Q&A compatibility for translated Specs. You can (and should) write your entire Mass Update (exept for Global Code) in one element, to ensure that you are accurately controlling the execution order. Then, you can use Ctrl-A to select the whole thing and clear it.

The only exception to this  is if you are, as Mark says, wanting to separate bits of your Mass Update for debug purposes or for use on different occasions. Then, if they are in separate elements, it's easy to turn pieces on and off.

Quote:

The word clear (in "Clear All") does not refer to the programming content, it refers to the intent to run a particular portion of that content.

Quote:

Not a workaround. If we cleared the programming because you hit clear in the spec (as opposed to in the programming itself) - we might well be deleting what took hours or days or weeks to create. If we don't reset the "P" when there is programming in that event, we would get a lot of people complaining that we didn't notice their programming and how are they supposed to be able to find it (since without setting the "P" there is no indication there is any programming in that event). So the only viable way to clear programming (not the intent to run programming) is to actually clear the programming out of the programming editor. This makes it a very explicit and clear statement on the users part, in which we do not have to infer or guess their intent in any way.

One way to consider this: if Sesame turns on a spec's "active indicator", it is Sesame telling the user there is something there to run. If the user turns it off, that is the user telling Sesame to not run that specific portion.

Quote:

Ray is looking into it. So far search is finding words without problem whether or not there is a space following that word. It will even find parts of a word in the middle. It is, however, case sensitive.

Mark,

I tried the "find' in my program and this time was able to find my requests. Knowing that it is case sensitive HELPS, but with words like

FormResultSetCurrentPosition("LineItems")

I vote that Find be 'case INsensitive', or a check box so the user can select depending on his needs.

Thanks for listening.

Steve