Hi!

>I've done this before in similar situations so I wouldnt think your too off base here. You might want to look at spreading the load around a little and have some cursors created at startup under the guise of the splash screen, then create your final cursor to drive the combo when the form is launched.

I am even entertaining the notion of downright copying those tables to the local hard-drive upon startup. Back in my clipper days I would copy all the rows from a combo table into a static array the first time they were used so that everything would move faster.


>About the only thing I havent seen you propose is a view based on a view,

Roxanne, are you placing bets about what crazy schemes I'm going to come up with???? ;-)

A view on a view hasn't occurred to me. How would that speed things up?

Indexing a view like the framework does wouldn't really help me as in most cases I'm dealing with a single row of data.

>>A number of the fields in these tables come from comboboxes where the user can choose from a list or also type a new option, so we ended up with "X-RAY", "X-Rays", "X RAY", "X RAYS", etc. I created queries to extract unique data from these fields to populate MY combos and that's how I ended up with those huge sets of choices. Of course, once we migrate, they will start cleaning all this up and hopefully my combo's will go down to reasonable 20-50 choices, which is really all they need.
>
>so your performance concerns are only for an intermediate time period until the data is cleaned up?

Some are (combos), some arent (like the query I posted in my first message). There are delays I don't worry about too much, but there are others that I know will eat into the performance of the final app.

That's not pretty, you do all this work now to make your combo's faster, then the data sources get cleaned up and it's overkill.

One thing I'm not in control here is how long it will take them to clean the database. However, I'll try to have them allow me to do most of the cleanup work as it would be more efficient.

Thanks for your tips!

Alex