3/20/2024 0 Comments Scriptcase search on event![]() ![]() It is when the onScriptInit for the whole app (NOT the search onScriptInit) that the values are added to the WHERE. Then the grid processes the search, which really does nothing as far the ‘fake’ fields are concerned. When I click advanced search button, I can put anything I want in those fields. onScriptInit This event runs when the application is loading. onNavigate This event runs when navigating from one record to another one. When the app loads the 2 fake search fields are empty by default. Here is a list with the most used events in each application in Scriptcase: Form Events onApplicationInit This event runs when the application is loading just for the first time. ![]() When closing the PHP tag in a Scriptcase event, the executed language is HTML. The title_search is a global OUT I use in the layout header. search events General Overview General Overview Most Scriptcase applications, with the exception of Tabs and Dashboard applications, have events that can be used to create business rules, validations and changes to the application’s CSS, among other things. (I had to do this because the encryption SQL code that works elsewhere in the app caused errors in search code. In the grid’s event onScriptInit (NOT the search onScriptInit) - searchname and searchaddress are ‘fake’ fields I created in advanced search…No corresponding fields in DB. ![]() Yes unfortunately, the macros in thr search events do not seem to add anything to WHERE, so this is what I did (SC bug?). So I also needed to create some ‘fake’ fields in the advanced search, and intercept the values, then slip those in the special WHERE using the AES_DECRYPT). (I use AES_DECRYPT in the SQL Select and preparation boxes and other events to do it FYI, but that is another post LOL). This interface has the options for you to select and set the Search application required fields. On a grid app I am using aes_encryption, so I am not able to directly use the advanced search (or any search) for those fields. You and I always seem to be trying the same things LOL. I know this is a year old post - but I figured out something just today on same thing. For information about the timing of events execution or other information, access the documentation of the desired event. During this playlist we are going to show. Scriptcase’s macros are special variables that allow the user to manipulate events, buttons, applications, security control, manipulate with dates, etc. My friend! Sorry I haven’t skyped in like forever. This macro identifies the selected menu item and other macro identifies the name of the application that was selected from the menu. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |