I am having some trouble with a VBA form. When I load the form from a macro that is called from within a participant record UI form, none of the events within that form fire (ex on click for a cmd button). If I call the form differently, it works fine. I am guessing it is cased by the modal participant form. Opened a case, waiting for response. If anyone has any idea, would be appreciated. Thanks, William William da Silva ---------------- eSimpleIT [Email Removed]

William, From my experience events are not fired when you have code that opens an object's GUI window. This is very annoying as you would want all the other code to apply to this window as well as one opened directly from RE. However if you implement the IBBAPIListenerCallback and then add the CAPIListener to your project initialising with the implemented callback object then the events will be fired and you can capture them. David Zeidman Development http://www.zeidman.info

I think I might not have explained myself properly (or I don't understand your answer). The events that don't fire are within my custom form, like an on click of a button, not RE event triggers. The way I call the form is from within a participant record. When in RE, you have a participant record open, and you go in the toolbar on the little VB icon and call a macro. This macro loads the form. The form loads properly, but events within this form do not fire. William da Silva ---------------- eSimpleIT [Email Removed]

OK now I understand what you mean. If I do UserForm1.show and have a button on the form then the events do not get fired. However if I do UserForm.show vbModal then the events are fired. David Zeidman Development http://www.zeidman.info

pretty sure I tried that one already. Will try again... William da Silva ---------------- eSimpleIT [Email Removed]

Just tried it. I still can't get it to work. I even did a simple form with one button and a msgbox. This is my macro in system_macros Public Sub TestMacro(obj As IBBDataObject) UserForm1.Show vbModal End Sub if I call it from the event record, it works. If I open a participant and call it from there, it does not work. William da Silva ---------------- eSimpleIT [Email Removed]

So I have now tried the macro three different ways. 1. From the event record, opening a participant 2. From the constiutent record opening a participant 3. From a participant query It works for all but the second one. I guess this is the one that you tried. Strange. Not sure why it shouldn't work there. The participant record from a constituent record is also modal but it works there. David Zeidman Development http://www.zeidman.info

Actually, mine did not work when I open a participant from an event record. What version are you on? I am on 7.80.1122.19 William da Silva ---------------- eSimpleIT [Email Removed]

Sorry my mistake. My testing was the same. It does not work from an event but does from a constituent or query. David Zeidman Development http://www.zeidman.info

William, I've had a similar problem with this in the past and there appears to be no solution. The problem appears when a VBA form is run from an RE form that has been opened modally (ie forms which, when open, do not allow focus to shift to any other within RE - eg Address, Participant, Relationship). I opened a case and recieved an excellent reply from the programmers which I now can't find. I think it had something to do with the fact that VBA was called from the forms process rather that the application's - the non-visual code could be executed but as focus could not shift the events on any forms would not be captured (if that makes sense!) I eventually gave up on it. David: Am have seen the CAPIListener, but have yet to try it, do you perhaps have a sample implementation as my knowlege of callback function is limited (ie zero) Regards Wayne

I opened a case with BB and yesterday got an excellent response from Katie Hawes. As I suspected, and as you mentioned Wayne, the problem is called by the modal form. Normally, you would be able to pop up a modal form on top of an other modal form and have it work. In this case however, it would seem that the VBA modal form cannot be properly used on top of the application's modal form which is in vb6. Katie had an excellent workaround which I have yet to try. She recommended that I create my form in VB6, compile it as a dll, reference it in my VBA and call the form this way. She has tested it and it would seem that it works. Thanks for your help David and Wayne. William da Silva ---------------- eSimpleIT [Email Removed]