Access File/Get Data can't attach to a SQL table.

[Bob C.]

In Access 97, I am trying to attach to a table in my SQL Server 2000
db.

I use File/Get Data, which displays all the SQL tables including the
one I can't attach to. (I can attach to all the other SQL tables.)

But, when I select that table I get a message that tells me the name
is invalid. I don't understand this because it gives me the name in
the Get Data dialog, and I don't have to enter it manually.

Any ideas?

Thanks,

Bob C.

[Christopher Secord]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Bob C." <bc******@bmghomes.com> wrote in message
news:2e**************************@posting.google.c om...

But, when I select that table I get a message that tells me the name is invalid. I don't understand this because it gives me the name in the Get Data dialog, and I don't have to enter it manually.

There are two possibilities that I can think of. It could be a
permissions issue with the file, or it could have something to do
with the file name. What is the filename anyway?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32) - WinPT 0.7.96rc1

iD8DBQFAPljWM39tsRlF0f4RAlXcAJkBMpWHojQ917bRPejK6L r0oX/LAACfdpab
P+ZyeV7v8sku9JdGzXHvcYY=
=ofVq
-----END PGP SIGNATURE-----

[Bob C.]

The table name is "CommunityCommissionDetail".

Among the possible problems listed in the message, the only one that
made any sense was: filename may be too long.

But, I have two tables with slightly longer names that attached and
work just fine.

Thanks.

Bob C.

[Christopher Secord]

-----BEGIN PGP SIGNED MESSAGE-----

Hash: SHA1


"Bob C." <bc******@bmghomes.com> wrote in message

news:2e**************************@posting.google.c om...

The table name is "CommunityCommissionDetail".

I guess it's not the name then. I just did a little test and was

able to link to a table with that name.


The only other good idea I have is that the table is owned by another

user. What are the permissions on the table in SQL Server?


Also, can you post the create script for it? This is a long shot but

maybe it has something to do with a certain data type.


-----BEGIN PGP SIGNATURE-----

Version: GnuPG v1.2.1 (MingW32) - WinPT 0.7.96rc1


iD8DBQFAP5l5M39tsRlF0f4RAmFOAJ4j6/BP9y4NKD0N4VfoX1ZgyQpKhACfau2C

Ijty++xwLOXqbvxmvznvbSg=

=qK5T

-----END PGP SIGNATURE-----