>Ditto to what Charles suggested.
I say sincerely without any sarcasm it is a milestone in my .net evolution to get dittoed by Bonnie <bg>
>
>~~Bonnie
>
>>Hi,
>>
>>I have the following scenario of using a lookup on a form:
>>
>>I have a user control that has a text box and a button. The user control resides on the form (call it parent form). When user clicks on the button a modal form (call them Lookup form) is opened with a grid showing data from a database table. This data is in a dataset that is retrieved from the database via call to a stored procedure. The dataset can be retrieved when the Lookup form is instantiated. The problem is that user clicks on a lookup button and selects an item from a lookup form, then closes it (moving to another control on the Parent form). So every time user clicks on a lookup button the program has to make a trip to the database to get the data.
>>
>>Is there a way to make the retrieved data set remain in the memory in order to minimize trips to the database?
>>
>>One scenario I am thinking is that the data set can be retrieved in the parent form. Then I would assign the data set to a field of the parent form. But how would the lookup form (the one called from click on the lookup button) would have this dataset "visible"?
>>
>>Any suggestions will be greatly appreciated.
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.
