Is there a difference between a manual button push and a PUSH() in Xbasic?
I an trying to create a dual purpose ENTRY/EDIT interface for an invoicing system. My problem has been with the entry design side of things. I have a main menu with a number of buttons on it. One button is called ENTER NEW INVOICE. When this is pressed it puts the value "entry" into a variable called ventryedit. It also opens the invoice table and enters a new invoice record then it closes the INVOICE table. It then calls up a form called ENTRYEDIT.
This form has a browse and also a button which calls up another form called EEINVOICE. The ENTRYEDIT form is for viewing only and the EEINVOICE form called up by the button is for entry/editing purposes.
So from the users perspective the interface requires too many keystrokes. First he has to press the ENTER NEW INVOICE button on the main menu. Then he sees a new screen (ENTRYEDIT) which contains a browse listing the new record that he has created, this browse is read-only so in order to work with this record he has to press another button to finally bring up EEINVOICE. The setup works very well and is quite reliable.
So I thought it would be a snap to set it up so that the usercould sidestep the unnecessay button press in ENTRYEDIT to call the EEINVOICE form. The idea is to set up the ONINIT event of EEINVOICE to look for the word "entry" in the ventryedit variable and to have the code run PUSH() on the button to call up EEINVOICE. It didn't work I ended up with two instances of EEINVOICE only one of which closed when the user exits from the main menu. I have tried putting the push() code in the activate event with no success. Any suggestions?
I an trying to create a dual purpose ENTRY/EDIT interface for an invoicing system. My problem has been with the entry design side of things. I have a main menu with a number of buttons on it. One button is called ENTER NEW INVOICE. When this is pressed it puts the value "entry" into a variable called ventryedit. It also opens the invoice table and enters a new invoice record then it closes the INVOICE table. It then calls up a form called ENTRYEDIT.
This form has a browse and also a button which calls up another form called EEINVOICE. The ENTRYEDIT form is for viewing only and the EEINVOICE form called up by the button is for entry/editing purposes.
So from the users perspective the interface requires too many keystrokes. First he has to press the ENTER NEW INVOICE button on the main menu. Then he sees a new screen (ENTRYEDIT) which contains a browse listing the new record that he has created, this browse is read-only so in order to work with this record he has to press another button to finally bring up EEINVOICE. The setup works very well and is quite reliable.
So I thought it would be a snap to set it up so that the usercould sidestep the unnecessay button press in ENTRYEDIT to call the EEINVOICE form. The idea is to set up the ONINIT event of EEINVOICE to look for the word "entry" in the ventryedit variable and to have the code run PUSH() on the button to call up EEINVOICE. It didn't work I ended up with two instances of EEINVOICE only one of which closed when the user exits from the main menu. I have tried putting the push() code in the activate event with no success. Any suggestions?
Comment