Create Query Object vs Hard Code

[sstiebinger]

I'm new to Access so I'm sorry if this is a bit Naive but... Why would I create a query database object for a row source instead of just typing the query directly into the row source for a form/report/etc?

[Perceptus]

Do you mean DDL or coding a querydef?

[ranman256]

you can put the query name in it... qsMyClients
or you can click the elipsis button and BUILD the sql in it.

I prefer the query name.

[sstiebinger]

I meant coding a Querydef vs typing the query directly into the rowsource of the object...

I understand that the querydef is technically faster, but where performance is not an issue is there a reason? Other than preference?

It seems to me that having a large number of query objects in the database seems superfluous and makes documenting the database that much more complex....

[June7]

I prefer fewer query objects and use SQL statement in RowSource and RecordSource whenever possible. I don't know that reference to query object is faster.

[sstiebinger]

Thank you, that's helpful.

I've taken over an existing app that the previous person has created object for each query... and I found it much more difficult to document.
Plus, there are queries that were created for forms or reports that were later abandoned which I find is even more of a reason to not create the objects.