Hi Vlad & Tim,


Tim said:
>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?


We use a shared connection on our MSSqlServer back-end and we mainly use remote view. I'm not sure how many there are, but it's a lot! We do use SPT also, but not as much.


Vlad said:
>Remote views is not a bad idea until you have a LOT of them. Say, you have 10 forms that work with 20 tables that require, say, 30 views only for main data. When you have 3-4 comboboxes/listboxes that require data lookup, 10*4 = 40 additional views for each combobox. 70 views in the database is quite bad idea.


We solved the combo data lookup problem like this: We have a few tables on the SQL backend that are used only for combo box lookups ... and there could be sometimes 5 or more of these combos on one page/form, which as Vlad said, would be a lot of overhead to get the data for these from the backend for each combo. So, we keep a local .dbf table just for these few tables (at application start-up they are updated if the data has changed on the backend, or created if they do not already exist ... this is data that does not change frequently once it has been customized).

Hope this gives you some food for thought ...

~~Bonnie