Hi!

Yes - a slow opening of the database and views from it, specially through LAN.

For little queries like lookups and other read-only things it is a good idea to use just a SELECT-SQL statement instead of view. Remember that resut of SELECT statement could be made writable, so read-only is not an issue here. Leave only views that require edits. In addition, join several views into a single one by using more parameters for views.

To organize better SELECT statements so they will be generic enough as views (for case you plan to upsize application to anotehr backend in future), create a finction that will run a query string for you using a query name. Store all queries in some table with name (ID). Later it will be very easy to change the function for runnign such queries to use remote data source.

In case of remote views, it is a good idea to use SQL Pass-Through functions for querying read-only data instead of views.

>Hi,
>
>are there any problems with having a large number (1000+) of remote views in a DBC?
>
>Thanks for any comments!
>
>Regards,
>Armin