Though I think I know how to solve this, having read the recent "Problem with Grid" thread, I wonder if someone can explain what's happening in the following situation.
I have a 'main' form which calls another, data-entry form. I've placed a grid on this data-entry form to show related information from a different table than the one the data's being entered into. Right now, when I pull up (make visible) the grid, it's just a white space, and that's want I think the information in the thread mentioned will solve. But I also find that when I re-run the program or enter the 'main form' again, and again switch to the data-entry form, a 'grid' appears covering the 'main form and it just sits there till I close it. Then the Data-Entry form (which is larger than the 'main form') appears - with the (blank) Grid where it's supposed to be.
I assume the SQL statement I'm using to populate the grid isn't being closed or released as it should be, but why does the thing(cursor or whatever it is) appear on the parent form instead of the child form, and only when I press the button to bring up the child? I assume it has to do with the order things are done in instantiating the form, but is this really the right way for things to work?
I have a 'main' form which calls another, data-entry form. I've placed a grid on this data-entry form to show related information from a different table than the one the data's being entered into. Right now, when I pull up (make visible) the grid, it's just a white space, and that's want I think the information in the thread mentioned will solve. But I also find that when I re-run the program or enter the 'main form' again, and again switch to the data-entry form, a 'grid' appears covering the 'main form and it just sits there till I close it. Then the Data-Entry form (which is larger than the 'main form') appears - with the (blank) Grid where it's supposed to be.
I assume the SQL statement I'm using to populate the grid isn't being closed or released as it should be, but why does the thing(cursor or whatever it is) appear on the parent form instead of the child form, and only when I press the button to bring up the child? I assume it has to do with the order things are done in instantiating the form, but is this really the right way for things to work?