I have a VFP 9 program where the user first makes a selection from a combo box, then clicks on a command button which brings up a popup screen where they enter some information, then a grid is displayed based on the information picked from the combo box and the data entered in the popup screen.
The combo box initial enable property is set to .t.
The command button initial enable property is set to .t.
The grid initial visible property is set to .f.
The grid contains 3 columns. The first column is text and the other two columns are combo boxes.
After the user clicks on an item in the combo box, the enable property is set to .f. This works as advertised in development mode, but in compiled mode, the combo box is re-enabled as soon as the grid is displayed. No place in my code do I reset the enable property for the combo box. I even put in the grid's gotfocus(), combobox.enable = .f. This had no effect. The same thing happens to the command button.
Has any one else run into the enable property behaving differently in compiled mode vs development mode in VFP9? I did not have this problem in VFP7.
Thanks for any advise
linmor26
The combo box initial enable property is set to .t.
The command button initial enable property is set to .t.
The grid initial visible property is set to .f.
The grid contains 3 columns. The first column is text and the other two columns are combo boxes.
After the user clicks on an item in the combo box, the enable property is set to .f. This works as advertised in development mode, but in compiled mode, the combo box is re-enabled as soon as the grid is displayed. No place in my code do I reset the enable property for the combo box. I even put in the grid's gotfocus(), combobox.enable = .f. This had no effect. The same thing happens to the command button.
Has any one else run into the enable property behaving differently in compiled mode vs development mode in VFP9? I did not have this problem in VFP7.
Thanks for any advise
linmor26