Thank you for your response! I was away for a few days and just got back.

We are using SQL 7.0 and one of our concerns is the number of connections in use. When the init method runs to load the data, are you using a shared connection?

Can you tell me why remote views are a bad idea?

...tim

>Hi!
>
>It is bad idea to have waste amount of views in the database. This slows down the opening of tables and views even when view opened with NODATA option. I prefer to use the Alias row source type. Then I have my own listbox and combobox classes that have custom property where you specify a query (or a query name if I have a maintained table of queries). In the Init in these classes I query the data into the alias specified as a row source. When I use the uqery management (queries stored in the table and ran by functiona using query name), I use this approach also for rids and many other things on the form. This way is flexible and very useful for case when you move to remote server backend, like SQL Server.
>
>>After approaching things many different ways we have settled into using an Alias RowSourceType for our ListBox controls. I will describe how we do this and I would like some ideas on how we might do this differently.
>>
>>Here are the options we considered:
>>
>>2. Alias
>>3. SQL Statement
>>4. Query (QPR)
>>5. Array
>>
>>We create a remote view for each listbox and name them the same (or similar). We use the advanced options to have the view share an existing connection.
>>
>>We add the view to the environment of the form. This makes it easier for our form designers to select the control source for the controls. Since we must share a connection we set the NoDataOnLoad to TRUE, and REQUERY() the views in the INIT method of the form.
>>
>>We appreciate your time and consideration…
>>
>>…tim