Blanks in ColumnNames causes ODBC-Error

[Andreas Lauffer]

I use Blanks in ColumnNames ( I know that this isn´t very good, but a
lot of code and querys had to be changed if I would remove all blanks
in all columnnames).
When I link this tables with ODBC in my ACC97 - project, some of the
tables causes an ODBC-Error.

Are there possibilities to workaround this error?

Thanks, Andreas Lauffer, easySoft. GmbH, Germany

[Albert D. Kallal]

You don't quite mention what you are linking to. (or what you are linking
from).

If you are using ms-access, then you are NOT using odbc if you are linking
to a back end table. That is a file share...and NOT ODBC.

However, you can usually put square brackets around the field name when
using JET.

[City Name] for example.

You are correct that most databases like sql-server etc don't support blanks
in the field names. A hard lesson to learn!

selectCityFromTableTest

select City From TableTest

As you can see, spaces are delimiter used to separate each keyword. Thus, it
is query easy to see how this should be avoided. You should not use spaces
for all objects such as reports, forms, modules, and yes..even field
names...
--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
ka****@msn.com
http://www.attcanada.net/~kallal.msn

[Andreas Lauffer]

Thanks for your answer.

You don't quite mention what you are linking to. (or what you are linking
from). OK, from Access97 to SQL-Server.
If you are using ms-access, then you are NOT using odbc if you are linking
to a back end table. That is a file share...and NOT ODBC. But the linked table have a ODBC-Connect-String. I use a DSN-less
connection.
However, you can usually put square brackets around the field name when
using JET. I could´t use brackets, because I just open the linked table in the
speadsheat-view (double-click), and got ODBC-Error, and all fields
contain #Name?


[City Name] for example.

You are correct that most databases like sql-server etc don't support blanks
in the field names. A hard lesson to learn!

selectCityFromTableTest

select City From TableTest

As you can see, spaces are delimiter used to separate each keyword. Thus, it
is query easy to see how this should be avoided. You should not use spaces
for all objects such as reports, forms, modules, and yes..even field
names...