Form Recordsource/Rowsource Queries: standalone or embed?

[Guest]

Are there any advantages or disadvantages to pointing form
Recordsource/Rowsource properties to stand-alone queries vs. building/storing
the statements inside the forms? E.g. is form load or execution speed
affected? Any other thoughts?

I can see a clear advantage to stand alone queries in that they can be
changed without modifying a form, but separating them from a form certainly
increases / clutters the query inventory (which might just be a cosmetic
thing ).

Chris

 

[Alex Dybenko]

Hi,
almost no difference, as Access creates hidden queries for sql statements in
recordsource,
I use sql statements in most cases

--
Best regards,
___________
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com

 

[kingston via AccessMonster.com]

If you are deploying the application as an MDE, users will not be able to
modify the data source. This could be good or bad depending on your
situation. Also, a visual query is available to more than one object whereas
an embedded statement is exactly that.