> In particular the problem is likely the GUID based index names create when
you[color=blue]
> setup relationships.[/color]
I think:
when you create relationships, you get relationship names based on
concatenating the two table names - so two long table names give you
a long long index name.
GUID index names come from importing relationships (?? or something
like that ??), and are ?? 38 characters long ??
so perhaps a solution is to first import all from the original
MDB into a new MDB. NOTE: make sure you have Jet 3.51 SR3
before importing relationships in A97: SR2 duplicated relationships
when importing.
(david)
"Tony Toews" <ttoews@telusplanet.net> wrote in message
news:tbhga0dn5o6eo2qk4ap4ul0veuk86s3778@4ax.com...[color=blue]
> Dimitri Furman <dfurman@cloud99.net> wrote:
>
>[color=green][color=darkred]
> >> I'm having problems with attaching two tables stored in an SQL Server
> >> 2000 to an Access 97 database. It worked well for all other tables
> >> except those two.
> >>
> >> This is what I did: Choose the data source from the ODBC dialog, choose
> >> the database on SQL Server login, select all tables in the SQL Server
> >> database. All tables were attached except the two, it says something[1]
> >> like "database module can't find 'dbo_<tablename>'".
> >>
> >> The name is not exceptionally long, a table with a 33-char name was
> >> attached, the name of first table that was not attached was 26 chars.
> >>[/color]
> >
> >Are there any indexes on these tables with the names that are longer than
> >64 characters? If there are, this would cause a problem with linking,
> >although I don't recall the particular error message you would get in[/color][/color]
that[color=blue][color=green]
> >case.[/color]
>
> Yeah, that's the problem. I knew I'd seen it before but couldn't recall[/color]
the details.[color=blue]
> (And it's at the bottom of my Random Thoughts on SQL Server Upsizing from[/color]
Microsoft[color=blue]
> Access Tips page at[/color]
http://www.granite.ab.ca/access/sqlserverupsizing.htm.)[color=blue]
>
> Error 3125 "The database engine can't find <name>. Make sure it is a valid[/color]
parameter[color=blue]
> or alias name, that it doesn't include invalid characters or punctuation,[/color]
and that[color=blue]
> the name isn't too long."
>
> In particular the problem is likely the GUID based index names create when[/color]
you setup[color=blue]
> relationships.
>
> To the original poster. Generate a SQL script via SQL Server Enterprise[/color]
Manager.[color=blue]
> Look for those long index names. Rename them. Recreate the SQL Server[/color]
database and[color=blue]
> reload the data.
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> Microsoft Access Links, Hints, Tips & Accounting Systems at
>
http://www.granite.ab.ca/accsmstr.htm[/color]
