3/8/2024 0 Comments Add a new license scriptcase![]() In this way, if it is in the NO ERROR state, we will be able to carry out procedures that we would not do if the form is incomplete and is not yet ready to be updated or entered in the DB, these procedures may include reforming the appearance of the form, fields, blocks, etc… If there has been an ERROR in the form, transforming tasks or calculations cannot be performed, the form must be left as initially entered in sc_btn_new until there are no errors in it. I know I can: remove the Form buttons buttons group in the Toolbar use the scbtndisplay(new, off) macro (I tried to use it in all events). Of course, it is checked if the operation carried out by the user is not a Delete, if it were, there is no need to check the variable in the onLoad event, but if it were Update or Insert if it is necessary to know if it returns to onLoad from an ERROR or NO. I’ve been struggling to be able to hide the New button in my grid. Sc_error_message(‘Los campos con * son obligatorios.’) If your calendar application is already created, we must add the fields below in the table so that the new functionalities work correctly: You can change the table structure with the ALTER TABLE function. Depending on the selection made from a primary field > 5) || If the true value of sc_btn_new cannot be preserved, for whatever reason, within the Scriptcase system when the insert button is pressed, Scriptcase could create a new macro called for example sc_validate_error and be able to act like this:Īlvagar, I put an example of my code in a simple form.Īs you can see (I’m telling you this in passing so you don’t get surprised when reviewing the code), I don’t let SC act directly on Required fields either! The form has fields that can be set to ‘not visible’. ![]() The user is only being informed to correct his input data and try to add the record again, so the form should remain in the state left by process 1, not execute process 2, which will possibly leave the form in other state, for example read-only or not visible fields, disappearing blocks, etc., for an update process, not for a new record. In this case, process 2 is executed, which should not be the case, since we are still in the process of inserting a new record, the only thing that has happened is that we do not allow it to be inserted as it is because some data is wrong. The form returns to the onLoad event, but sc_btn_new is no longer true, since it may have changed its value from true to false by pressing the insert button. …sc_message_error(‘Error’) sc_error_exit() Our documentation is continuously updated, according to the release of new features. When the user has entered their data, pressing the insert button, and in the onValidate or onValidateFailure event occurs: Access Scriptcases complete documentation online to check out all the available features, or download the documentation in PDF. ![]() In the onLoad event of a form if we present this process:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |