I think I upset Access 2003 :)

[Killer42]

I was playing around with some ideas in the SQL view, clicked "!" to try it out, then clicked to go back to design view.

Where my SQL had an embedded query including a bunch of UNIONS and so on, Access had made up the table name "%$##@_Alia s". I think it's getting annoyed with me. :D

[Dököll]

I was playing around with some ideas in the SQL view, clicked "!" to try it out, then clicked to go back to design view.

Where my SQL had an embedded query including a bunch of UNIONS and so on, Access had made up the table name "%$##@_Alia s". I think it's getting annoyed with me. :D

Did it create a table with errors? Did you get any sound data?

Where are you hoping to retrieve data, by the way?

[pks00]

I was playing around with some ideas in the SQL view, clicked "!" to try it out, then clicked to go back to design view.

Where my SQL had an embedded query including a bunch of UNIONS and so on, Access had made up the table name "%$##@_Alia s". I think it's getting annoyed with me. :D

Access loves reformatting, I hate using the design view, always use the sql view.
One thing I really hate is its love for brackets. Everything has brackets around it.
What u got is probably how access has tried to setup the query so it's viewable in design view.

So if possible, customise your toolbar and get rid of design view!

[NeoPa]

I'm no great fan of Acess's parentheses either I must admit, but I wouldn't go as far as losing the Design View. I like the way it does most of the donkey-work for me, but I always trim up the code if I'm reusing it elsewhere.
Killer, I guess you already know that what you got was nothing to worry about - hence the :D in the question. JIC - It isn't ;)

[Killer42]

Access loves reformatting, I hate using the design view, always use the sql view.
One thing I really hate is its love for brackets. Everything has brackets around it.
What u got is probably how access has tried to setup the query so it's viewable in design view.

So if possible, customise your toolbar and get rid of design view!

Sure, and while I'm at it I might as well get rid of that pesky keyboard and mouse. They do so clutter up the desk.

I only use the SQL view when I have to. Never have seen the need to edit what Access builds. Perhaps that will change, but the only reason I've started using the SQL view is because I'm sometimes working with UNION queries that aren't supported by the design view.

[Killer42]

I'm no great fan of Acess's parentheses either I must admit, but I wouldn't go as far as losing the Design View. I like the way it does most of the donkey-work for me, but I always trim up the code if I'm reusing it elsewhere.
Killer, I guess you already know that what you got was nothing to worry about - hence the :D in the question. JIC - It isn't ;)

Yeah, it wasn't a problem - just an observation. I think I did hit a "bad bracketing" type of error message once or twice while playing around with this, but it was no big deal. I just found it amusing that Access was apparently swearing at me.

If I need to write SQL, I generally use the Access design view to build it, then copy and paste. But I don't actually use SQL very often. Except for in this stats database I'm playing with, which is the one swearing at me. :)

And then I'm generally only playing with the SQL because of UNIONS and stuff that the design view doesn't like.