To be fair, if you're gonna be in access, their SQL query writing interface is a steaming pile of issues. In my experience: 1) You can't do multi-line queries.

To be fair, if you're gonna be in access, their SQL query writing interface is a steaming pile of issues. In my experience: 1) You can't do multi-line queries. After executing, it'll smash it all to one line again. 2) You can't add comments. After executing, it'll delete them out. 3) It doesn't do any syntax highlighting. ---- Years ago I worked for a company who had tons of manufacturing production data. Someone built an interface to query the data - used by just a couple people. Mind you, this isn't Access, it was homebrew software. Eventually word spread about the data you could access, and dozens to hundreds of people got access. They never got to the top of the priority list to make it multi-user, separate profiles, create permissions on queries, etc. There was a mandatory 8 hour training session with a test before getting access to the environment. Dev queries were automatically deleted 90 days since last run. On prod, 365 days. This was to reduce clutter. Query names were terse. You had to know people who knew what queries did. Comments were used sparingly. Anyone could edit and view any query available. I copied a query, made edits, then executed. Got weird results. It took 1.5 days to figure out the parser was messed up! First, line comments using ' were excluded. Next block comments using /* */ were excluded. However, if a macro was called inside a block comment, it was executed. That was the most frustrating bug I've ever debugged. Literally I'd copy the query, it'd run successfull, I'd comment out a couple returned values, and it'd fall on it's face because of how macros worked.