S
Scott Bryant
Hello
Has anyone else come across the following problem. On a couple of occasions
I have had need to use a passthrough query as a record set for a form to
improve performance on large databases - or to display data that an access
query is just a nuisance to use. In order for the users to be able to access
certain types of records I have had the form change the SQL for the Query
Definition that is used as the form's record source. In using this strategy,
it seems that the application becomes increasingly corrupt until ultimately
unusable. To get around this I use views as much as possible and find a work
around, but it is tedious when a set of data can be returned to the
application just as easily using a pass through query without the need to
create so many views in the back end data base. Is there a way to have this
happen safely or is it a matter of perserverance with the work arounds.
regards
Scott
Has anyone else come across the following problem. On a couple of occasions
I have had need to use a passthrough query as a record set for a form to
improve performance on large databases - or to display data that an access
query is just a nuisance to use. In order for the users to be able to access
certain types of records I have had the form change the SQL for the Query
Definition that is used as the form's record source. In using this strategy,
it seems that the application becomes increasingly corrupt until ultimately
unusable. To get around this I use views as much as possible and find a work
around, but it is tedious when a set of data can be returned to the
application just as easily using a pass through query without the need to
create so many views in the back end data base. Is there a way to have this
happen safely or is it a matter of perserverance with the work arounds.
regards
Scott