help with hidden relationship

  • Thread starter Thread starter schen88_98
  • Start date Start date
S

schen88_98

I have Access data that have been upsized to SQL Server, the
remainings are form, query and report on the Access part as front-
end. The upsizing was done by someone a while ago, and I see one
table is not associated with the other 3 tables, even though the pk/
code# matchs. For example, t1.code# equals to t2.code#, but there is
no relationship between them, or the relationship shows nothing.

I don't know whether this is the way when data are in SQL Server as a
back-end. From SQL server I can query to make reprot work.

Need help if it is all right to add the relationship again in the
front-end in this situation.

Appreciated.

Steve
 
I have Access data that have been upsized to SQL Server, the
remainings are form, query and report on the Access part as front-
end. The upsizing was done by someone a while ago, and I see one
table is not associated with the other 3 tables, even though the pk/
code# matchs. For example, t1.code# equals to t2.code#, but there is
no relationship between them, or the relationship shows nothing.

I don't know whether this is the way when data are in SQL Server as a
back-end. From SQL server I can query to make reprot work.

Need help if it is all right to add the relationship again in the
front-end in this situation.

Appreciated.

Steve

It's not really necessary to have the relationship in the frontend, though it
can be handy (when you create a query in the frontend, it automatically
includes the join specified in the relationship). The "real" - enforced -
relationship must be created in the SQL/Server database on the backend; it may
or may not be shown in the relationships window on the frontend. You'll need
to get into the Enterprise Manager in SQL Server to be sure that the
relationship exists and is being enforced.

John W. Vinson [MVP]
 
Back
Top