[AccessD] MacroError - VBA??

Or how access writes garbage in brackets in lieu of the nicely worded,
just-fine-the-way-it-was sql you just saved in the sql view. So you have
virtually no chance of parsing and rationalizing the sql property of the
query using code later in a statement. I call it aliening (as opposed to
aliasing, which I Access seems like it's trying to do).

M$ always helps Nize Master, very good,  follow M $$ ....