Hi,
I have no idea what development environment you are in, however leaving a
transaction open for any length of time is almost always a terrible idea.
It looks like the data in the drop down almost never changes? So read it
at application/middleware startup, and put it in some kind of list, and use
the list. (Client datasets work fine in delphi, there are plenty of lists
in java). You may want to refresh the list every day or so or at some
other timed interval.

david jencks

On 2001.06.07 19:57:01 -0400 Peter Morris wrote:
> I have a question.
>
> I finally got around the idea of having a dataset permanently open
> (desktop
> databases) and went with this approach in my apps
>
> 1) User enters code
> 2) Transaction starts
> 3) Record is selected
> 4) User alters data
> 5) Record is posted
> 6) Transaction commits
>
> Here is my query.
> If I want to provide lookup comboboxes on that same form, surely it is
> wasteful to select all records from the other table each time step (2) is
> reached ? Is it better to have a permanently open transaction in the app
> where these other records are already loaded ?
>
> Pete
>
>
> Community email addresses:
> Post message: IBDI@yahoogroups.com
> Subscribe: IBDI-subscribe@yahoogroups.com
> Unsubscribe: IBDI-unsubscribe@yahoogroups.com
> List owner: IBDI-owner@yahoogroups.com
>
> Shortcut URL to this page:
> http://www.yahoogroups.com/community/IBDI
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>