Hi Cetin,

for your understanding.

assume you have 4 logical parameters on a view and need a differnet result for each combination.
Some of these combinations need differnt subqueries
This will make a huge WHERE Clause.

Using the &? stuuf I create the needed code as a string and the view only rund the small code.
This makes the stuff a lot faster.


>Agnes,
>Assuming it worked somehow, wouldn't this cause a bloat in DBC (multiple drop/create for a view).
>Instead wouldn't :

>create database tmpDBC
>create SQL view as select ....
>
>* drop view whendone and remove dbc

The trick with the &?lcRequery is that I can change the view in his lifetime. What I mean is that the view is created, controlsources are bound to it and then I change the whole thing. It works as long as the result holds the same number of fields with the same fieldtypes.

If the view is once created with CREATE VIEW all changes are done in front of USE and REQUERY.
>... Or better a cursoradapter ?
Yes, there is a way to manipulate a cursoradapter to work like this. But the problem is that a lot of views are working like that and I need to redesign a lot of stuuf to change the views to CursorAdapter. Sooner or later I will do that - but there are some tiny restrictions on a redesign like that - let say the budget?

So what I'm looking for is a way to run it like version 7.00

Agnes