Well, I put a message in the code that sets IOOPTIONS.

I don't see the CREATE event firing nor do I see the CREATE activity display in the System Monitor.

So I guess IOOPTIONS doesn't get set at all. Any idea why this is happening?

Thanks,

rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

Ray,

Is this a promoted CREATE event that you are still having trouble getting to fire? If you can create a new form that will file the CREATE event then it might be worth your while to cut and paste everything from this current form into a new form just to move on. While it is nice to know why things break, sometimes it just isn't worth all the time and future project delays when you can do something else.

dbakke@srpcs.com

SRP Computer Solutions

Don,

I created a new Form and the Create event still is not firing. It is not a promoted Create Event.

I do have promoted GotFocus and LostFocus. I put a Msg call in my promoted GotFocus. I can see the msg there being displayed. Could something in the promoted events disrupt certain events from being fired. Actually I would think that I would see the Create Event happen before anything else.

Generally, I see the wisdom of your way – just fix it/copy it and startover. However, as it is, it doesn't look like the Create Events is being fired from any of my FORMS – new or old!

I think I will try removing some of my promoted event and see what happens.

rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

Don,

I didn't think Event processing was that complex, but the more I fiddle with OI the more impress I am with all that is going on as I look at the system monitor.

As best as I can figure out, my initial problem with the Create event not firing was caused by incorrect "structure" in defining my promoted GotFocus event.

That is, instead of using: "MyApp*GotFocus*Editline*Oiwin*"

I was using "MyApp*GotFocus*..Oiwin*".

In researching promoted events, I have a couple of simple questions. Hope you (or anyone for that matter) can provide some clarification.

1) When you make a change to or adding a promoted event, I see reference to "needing" to recompile forms. Is this just "saving" the darn form again?

2) The RETURN value in Event Handler can be either 1 or 0. My original understanding was that if an Event returns a 1 the event chain for ONLY that event will continue. If 0, the event chain for that event will halt. Based on my "experimentation", I see that stopping an Event can stop other type of Events from happening. For example, if on the LostFocus Event of the Keyfield returns 0, the Read Event will not happen.

This notion also appear to have some bearing on my initial problem. For example, a problem in my GotFocus promoted event prevented the Create Event in all form from firing.

Am I correct in my understanding/statement of Events. That is, returning a 1 to continue an Event flow can mean more than just continue the Event chain of that Event but could also enable other types of Event to occur – Again, LostFocus and Read; GotFocus and Create.

This may be all wrong, but if so, please let me know . This may also be all obvious to you and other, but boy it's a revelation to me.

If I'm completely off base, please let me know.

3) In researching Promoted Events, I have seen some reference to storing the promoted events in SP (StoredProcedure). If I use SP to contain my promoted events, does this mean changes made to the SP does not necessitate that forms be "re-compiled". All I have to do is just recompile the SP. Wow, that would be easier.

4) Lastly, if SP can be used, is there a way to have something like a commuter module for Promoted Events – one program to store all processes related to all Promoted Events. If so what parameters and how are parameters passed to the SP to tell it to execute the GotFocus or LostFocus or Whatever Events are possible.

Thanks,

rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

Ray,

3) and 4):

This posting of Don's will help you: . As it helped me.

- Oystein -

Ray,

1) When you make a change to or adding a promoted event, I see reference to "needing" to recompile forms. Is this just "saving" the darn form again?

If you change an existing promoted event you need to re-copy the object code to the SYSREPOSEVENTEXES and, AFAIK, you need to exit OI and go back in to avoid problems with cache storing the original event object code.

Re-compiling forms, if necessary, is not quite the same as "saving" the form again. The Form Designer will not always do a full re-compile if it doesn't think any changes have been made. I have found that making a quick change to a Window property and changing it back will fool the Form Designer. Another method that I prefer better is to use the Entity-]Compile menu from the Application Manager. Then I just double-click on one form after another. Goes much quicker than trying to load each form in the Form Designer.

2) The RETURN value in Event Handler can be either 1 or 0. My original understanding was that if an Event returns a 1 the event chain for ONLY that event will continue. If 0, the event chain for that event will halt. Based on my "experimentation", I see that stopping an Event can stop other type of Events from happening. For example, if on the LostFocus Event of the Keyfield returns 0, the Read Event will not happen. This notion also appear to have some bearing on my initial problem. For example, a problem in my GotFocus promoted event prevented the Create Event in all form from firing. Am I correct in my understanding/statement of Events. That is, returning a 1 to continue an Event flow can mean more than just continue the Event chain of that Event but could also enable other types of Event to occur – Again, LostFocus and Read; GotFocus and Create. This may be all wrong, but if so, please let me know . This may also be all obvious to you and other, but boy it's a revelation to me. If I'm completely off base, please let me know.

The key here is to understand when one event is responsible for triggering another event. In the case you cited, i.e. READ not triggered when LOSTFOCUS is returning a 0, is a classic case. The LOSTFOCUS event is responsible for checking the state of the key controls and seeing if a new key has been entered and therefore trigger the READ event. Obviously, then, if you return 0 in the promoted LOSTFOCUS event then the system level LOSTFOCUS event never gets triggered which in turn never gets the chance to trigger the READ event.

Sometimes you always want these future system level events to fire. You can use Forward_Event() to accomplish this, but just make sure you always Return 0 otherwise you will call the system level and subsequent events twice. Another alternative is to use the Send_Event() statement to explicitely call an event you know won't be triggered normally.

I do not know if GOTFOCUS is responsible for triggering the CREATE event. I would have doubted it but since I have not watched the System Monitor on this I can be certain.

3) In researching Promoted Events, I have seen some reference to storing the promoted events in SP (StoredProcedure). If I use SP to contain my promoted events, does this mean changes made to the SP does not necessitate that forms be "re-compiled". All I have to do is just recompile the SP. Wow, that would be easier.

Read the link Oystein posted first. The answer is "yes", you can store your main promoted event logic in a SP and simply use the promoted event object to call this SP. This will avoid the need to re-compile the promoted event, copy it into SYSREPOSEVENTEXES, and exit OI. However, I think you might misunderstanding when and why it is necessary to re-compile forms.

Once a form has been compiled the first time with a reference to a promoted event, then that form will not need to be re-compiled again. It does not matter how much you change the logic of that particular promoted event, only the reference to the event is stored in the form and that reference will not go away unless you accidentally remove the Enforce flag of that event and re-compile your forms. It is necessary to recompile a pre-existing form if you add a new promoted event. New forms automatically need to be compiled the first time and will store all existing promoted event references at that time.

4) Lastly, if SP can be used, is there a way to have something like a commuter module for Promoted Events – one program to store all processes related to all Promoted Events. If so what parameters and how are parameters passed to the SP to tell it to execute the GotFocus or LostFocus or Whatever Events are possible.

Again, read Oystein's link first. All you need is your own system for telling teh commuter module which type of event you are calling. Have enough generic parameters (i.e. Param1, Param2, Param3…) to account for events with many paramters. We go up to Param8 I believe. Just be careful to set your Return correctly. When you begin to store your event code in a commuter module it becomes easy to forget that you are still working in an event/function environment which requires an appropriate return value, i.e. 0 or 1. In our case, we pre-assign the return variable to 1 (which is usually what it needs to be) and then explcitely set it to 0 when the situation calls for it.

Hope this helps,

dbakke@srpcs.com

SRP Computer Solutions

Don,

Hope this helps,

You bet. I'm looking at the referenced link (4/12/99) and will run some test tomorrow. Thanks for taking the time to answer my questions.

Ray

rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

Don,

Hope this helps,

You bet. I'm looking at the referenced link (4/12/99) and will run some test tomorrow. Thanks for taking the time to answer my questions.

Ray

rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

Oystein,

As usual, many thanks (mange take(?)).

Ray

rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

Trenton makes, the world takes.

garygnu@compuserve.com

Takk til Alta Vista og Web som gjorde at jeg skjønte hva Gary mente med dette!

Oystein,

]]Takk til Alta Vista og Web som gjorde at jeg skjønte hva Gary mente med dette!Symmetry Info[/url]

Ray Chan ~ Symmetry Info

Don (any anyone else),

Earlier this month you helped me with an explanation of certain aspect of Promoted Events. Unfortunately, I'm revisiting it now; it seem so long ago. If you don't mind, I have a few questions.

1) Recompiling forms: You suggested the Entity-]Compile Menu. When I looked at this, my "compile" option is "grayed out." Is there a something else I'm supposed to do? It's probably simple.

2)At one time, I had my promoted events working. I copied the Event item related to a form to SYSREPOSEVENTEXES. Any case since then after experimentating with moving my promoted events to a Stored Procedures for easier long-term maintainance things are not working as well.

My promoted eventes are stored in a Function called Promoted_Events. Promoted_Events is the commuter module. Basically, it looks like this:

Function Promoted_Events(xx1,xx2,xx3,xx5)

Locate xx1 in EventList……

rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

Don (any anyone else),

Earlier this month you helped me with an explanation of certain aspect of Promoted Events. Unfortunately, I'm revisiting it now; it seem so long ago. If you don't mind, I have a few questions.

1) Recompiling forms: You suggested the Entity-]Compile Menu. When I looked at this, my "compile" option is "grayed out." Is there a something else I'm supposed to do? It's probably simple.

2)At one time, I had my promoted events working. I copied the Event item related to a form to SYSREPOSEVENTEXES. Any case since then I have been experimenting with moving my promoted events to a Stored Procedures for easier long-term maintainance. However, things are not working as well now. I know I'm missing something.

My promoted events are stored in a Function called "Promoted_Events". Promoted_Events is the commuter module. Basically, it looks like this:

—Commuter Module—

Function Promoted_Events(xx1,xx2,xx3,xx5)

Locate xx1 in EventList…… Then

 On Gosub GotFocus, LostFocus...

 Return

End Else

End

GotFocus:

* set background color

* select "text"

Return

LostFocus:

* return editline color back to "white"

Return

---

Since we are still working with in an Event Environment, where do you return the 1 or 0? In the function GetFocusEditField?

-]Below is function used by "Promoted Event GotFocus.EditField.Oiwin*"

Function GetFocusEditField

Declare Function Promoted_Events

* This is copied to:

* run *copy_row "SYSOBJ","$GetFocusEditField","SYSREPOSITEVENTEXES","SYMMETRY*GOTFOCUS.EDITFIELD.OIWIN*"

Return Promoted_Envents("GotFocus",CtrlEntId,CtrlClassId,CreateParam)

---

As you can see, it's largely cloned from examples that you have provided on RTI discussion forum.

Thanks,

Ray Chan

rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

Enter=Submit This Topic"

Opps. Please ignore this. Read Earlier message.

rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

Ray,

Although I am not Don or one of the other gurus here ..

I would guess that you have selected a 'exe' as in Forms Exe or Event Exes instead of the Form/Event

The button grays because you can't compile and exe

dsig@teleport.com onmouseover=window.status=imagine … a company that supports it products with pride not extortion;return(true)"

David Tod Sigafoos ~ SigSolutions

cell: 503-341-2983

Dave,

Well, I didn't say "Don or gurus". I said "Don and anyone else." Therefore, you would qualify . On the "guru" issue, however, you are one of the legitamate "gurus", stubborn, difficult, uncooperative, but a "guru".

Also, thanks for the tip. You were right on – See, you are a 'guru'

Chiao,

Ray

rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

I think Zappa fans spell it geroo.

- Oystein -

]I think Zappa fans spell it geroo.

How did you know ..

dsig@teleport.com onmouseover=window.status=imagine … a company that supports it products with pride not extortion;return(true)"

David Tod Sigafoos ~ SigSolutions

cell: 503-341-2983

David,

Saw it in my kristl bol.

No, I saw it in the lyrics sheet for Apostrophe' of course.

:– (attempt at Zappa emoticon)

- Oystein -

View this thread on the forum...