P
PeteCresswell
I've got a situation where I may be charged with ad-hoc reporting
against a SQL Server DB.
Do do that, I need to know how about a half-dozen tables relate to
each other. It's gonna throw me a .PDF of the DB's relationships
diagram and say "Figure it out". Problem is that said diagram is
about 250 8.5x11 pages and, to me, that means 2-3 hours of cutting/
aligning/taping to get a picture.
There are less than a half-dozen tables I'm unsure of. I know their
names and my suspicion is that if I could capture the SQL Server's
tables and relationships into a JET DB, I could dope it out a lot
faster.
Assuming that relationships are not implemented via triggers, is there
any hope here?
against a SQL Server DB.
Do do that, I need to know how about a half-dozen tables relate to
each other. It's gonna throw me a .PDF of the DB's relationships
diagram and say "Figure it out". Problem is that said diagram is
about 250 8.5x11 pages and, to me, that means 2-3 hours of cutting/
aligning/taping to get a picture.
There are less than a half-dozen tables I'm unsure of. I know their
names and my suspicion is that if I could capture the SQL Server's
tables and relationships into a JET DB, I could dope it out a lot
faster.
Assuming that relationships are not implemented via triggers, is there
any hope here?