It's not criticism. It's good database design to not use spaces in the
table names. And, it was not criticism to tell you that you that .NET
isn't scripting.
Now, perhaps if you took a breath and gave us more information, we could
help you. You could start by telling us why your tables need to have spaces
in their names. Maybe we could suggest a work around. But the first piece
of advice you are going to get if you just tell us that the spaces in your
table names are causing problems it to solve the problem at the source.
"Oggdorf" <Og*****@discussions.microsoft.com> wrote in message
news:A8**********************************@microsof t.com...
Thanks for the reply, however I know what i'm doing and why. Neither the
criticism "(that's database design 101)", nor the ignorance ".NET doesn't
use
scripts" assist me in resolving what appears to be a bug.
"Scott M." wrote:
You should go back and rename the table names to not have spaces in them
(that's database design 101). Also, .NET doesn't use scripts. It is
compiled code.
"Oggdorf" <Og*****@discussions.microsoft.com> wrote in message
news:D6**********************************@microsof t.com... > The table names in my database schema have spaces. When the .tab files
> are
> created in Visual Studio, the constraint names do not have brackets
> around
> them causing a syntax error.
>
> Is there a setting to turn brackets on at all times? This is the only
> situation where it is a problem, all other table name references in all
> other
> scripts contain brackets.
