By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,255 Members | 2,575 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,255 IT Pros & Developers. It's quick & easy.

Link Tables to SQL Error

P: n/a
I'm linking a bunch of tables that are in SQL to my Access db and I get
the following error on 3 of the tables: "Seq.Group is not a valid
name." I tried doing an import instead of a link, but I got the same
error. ???

FYI I am not the SQL dba and I'm not able to change table names or
reload data. I need a way around this issue stat!!

Thanks,
Shelley

Aug 16 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
FYI I'm using Access 2002 (XP).

Aug 16 '06 #2

P: n/a
sbowman wrote:
I'm linking a bunch of tables that are in SQL to my Access db and I
get the following error on 3 of the tables: "Seq.Group is not a valid
name." I tried doing an import instead of a link, but I got the same
error. ???

FYI I am not the SQL dba and I'm not able to change table names or
reload data. I need a way around this issue stat!!

Thanks,
Shelley
SQL apparently allows characters in table names that Access does not.
Unless you can get the name changed on the server or have a view created on
the server with a proper name then you will not be able to create the link.
At least not through the linking wizard. Creating the link via code "might"
work. I'd have to test that.

Have you tried a passthrough query instead of a link?
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Aug 16 '06 #3

P: n/a
Rick Brandt wrote:
sbowman wrote:
>I'm linking a bunch of tables that are in SQL to my Access db and I
get the following error on 3 of the tables: "Seq.Group is not a valid
name." I tried doing an import instead of a link, but I got the same
error. ???

FYI I am not the SQL dba and I'm not able to change table names or
reload data. I need a way around this issue stat!!

Thanks,
Shelley

SQL apparently allows characters in table names that Access does not.
Unless you can get the name changed on the server or have a view
created on the server with a proper name then you will not be able to
create the link. At least not through the linking wizard. Creating
the link via code "might" work. I'd have to test that.

Have you tried a passthrough query instead of a link?
Just tested. Apparently you have field names with periods in them. That
will not work in Access even when creating the link in code.

Tell the creator of the tables that he needs to fix them or create a view
with proper names that you can link to. IMO anyone that would put special
characters in a field name doesn't know what he's doing.

A passthrough will work, but the field name will show up as only the portion
after the period. That will make it difficult to work with because criteria
still has to be applied to the illegal name with square brackets around it.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Aug 16 '06 #4

P: n/a
Bri


Rick Brandt wrote:
Rick Brandt wrote:
>>sbowman wrote:
>>>I'm linking a bunch of tables that are in SQL to my Access db and I
get the following error on 3 of the tables: "Seq.Group is not a valid
name." I tried doing an import instead of a link, but I got the same
error. ???

FYI I am not the SQL dba and I'm not able to change table names or
reload data. I need a way around this issue stat!!

Thanks,
Shelley

SQL apparently allows characters in table names that Access does not.
Unless you can get the name changed on the server or have a view
created on the server with a proper name then you will not be able to
create the link. At least not through the linking wizard. Creating
the link via code "might" work. I'd have to test that.

Have you tried a passthrough query instead of a link?


Just tested. Apparently you have field names with periods in them. That
will not work in Access even when creating the link in code.

Tell the creator of the tables that he needs to fix them or create a view
with proper names that you can link to. IMO anyone that would put special
characters in a field name doesn't know what he's doing.

A passthrough will work, but the field name will show up as only the portion
after the period. That will make it difficult to work with because criteria
still has to be applied to the illegal name with square brackets around it.
Just speculating, but if the view was created with the fields aliased to
names that Access would allow, he should be OK. Without the View, a
passthrough (also with Alias' for the field names) would be another
option as long as the tables don't need to be updated (unless updated
via another passthrough of course).

--
Bri

Aug 19 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.