-
SQL in VBA
Just another general question: when would you consider using SQL in VBA rather than in SQL Editor?
-
General when you the queries are action queries, like delete, update, append, create, alter etc.
-
Because i have read that most of professional db developers tend not to save quires at all, but rather have them running in VBA. is it correct? what would be the most optimal way to learn and approach this matter?
-
I generally only build SQL in VBA when it's dynamic (the structure will vary based on user selections. Sometimes when it's really simple (DELETE * FROM TableName). Most of my queries are saved. Saved queries are compiled and will run faster (whether you'll notice the difference is another matter). I won't pretend to speak "most" developers, but I know a lot of very good developers that do something similar.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules