on 03-06-2007 8:39 PM
The EventHadler cannot be made the only procedure to expose all the events occuring in SAP B 1. It works fine when one adds a form or two or just a couple of controls on an exisiting one.
Things are a little different if you have to build a whole module with several forms and controls for which to evaluate. Imagine how long a single SBO_Application_ItemEvent would end up being!
I recently found out and had to divide the procedure ... so now my SBO_Application_ItemEvent has become basically a procedure that calls a whole bunch of other procedures and functions.
I thought I would just mentioned this. Things that could turn each one of us SAP Developer's life a whole lot easier ...
Cheers!
Neftali hi -
you may use B1DE addon wizard to simplify your event handling code. This
wizard is fully integrated with Visual Studio .NET and generates for you an
addon in C# or VB.NET based on a set of best practices of course on top
of SDK.
The code hides the ItemEvent and present event handling with a set of
listeners called when a given event is raised on a given form or menu.
You can download the whole B1DE package for free here on SDN
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.