SQL vs. Query

[Chrisopia]

I was told once upon a time, it's worth learning SQL to replace queries as queries bulk out the frontend. So to increase efficiency and reduce memory I thought to convert all my queries in my databases into SQL...

so row sources become SQLs, my append queries become INSERT INTO commands, and so on, so I have 1 or 2 queries, if that, left over. Then everything is run as SQL.

I thought it was logical as the query is just a user friendly way to create SQL anyway?

Or am I mistaking and wasting time?

What do you think?

 

[pbaldy]

You are correct that the query design grid is simply a visual user interface that creates SQL. If you're talking about executing SQL from a macro or VBA code, there's a trade off. Yes, you save an object in the front end, but a saved query is compiled and executes a little faster than the SQL executed from code. Personally, I usually use the saved query.

By the way, your example of a row source is not likely doing what you think. Putting SQL in the row source would save you the clutter of seeing the object in the database window/navigation pane, but Access actually creates a hidden, saved query, so you don't save any "bulk".