SQL database Joins
Dear Digital.
I have just upgraded to the pro version and am working though the
example on the end-user application linking to SQL server 7.
I have 2 questions.
1. Is this also OK with SQL Server 2000?
2. When the join table is automatically generated, it searches tables for
fields with the same name. Without wanting to get into a long debate on
naming, I can say that the name of the primary key field in one of my tables
is never the same name as the secondary key field in a related table. All of
the created joins are therefore no use. I can see how to manually create the
joins, however the database already knows this, so why is the join
generation not reading the database properties and finding out what the join
field names are? Is there a way to do this?
regards
--
John Evans
Technical Director
Clear Advantage Ltd
www.Clear-Advantage.co.uk
I have just upgraded to the pro version and am working though the
example on the end-user application linking to SQL server 7.
I have 2 questions.
1. Is this also OK with SQL Server 2000?
2. When the join table is automatically generated, it searches tables for
fields with the same name. Without wanting to get into a long debate on
naming, I can say that the name of the primary key field in one of my tables
is never the same name as the secondary key field in a related table. All of
the created joins are therefore no use. I can see how to manually create the
joins, however the database already knows this, so why is the join
generation not reading the database properties and finding out what the join
field names are? Is there a way to do this?
regards
--
John Evans
Technical Director
Clear Advantage Ltd
www.Clear-Advantage.co.uk
This discussion has been closed.
Comments
My guess is that to support all sorts of database engines, that
ReportBuilder doesnt get into specifics at the join level. I haven't used
to any great extent the heavy duty SQl databases, but I have used a number
of others and each have different methods of defining join properties.
As I provide an end-user solution I have used quite successfully the
dictionary support within ReportBuilder, where you are able to define the
joins in a table, which then makes the task alot simpler for the end-user.
You can also save data templates which can be re-used by end-users so that
they do not have to create the views themselves. It works great to be
honest, however I believe it does require the Enterprise version.
If I've completely misunderstood your second question then just ignore me,
most of my friends do anyway
Alex
2. The Data Dictionary component in RB is the way to go. Both the
Professional and Enterprise editions include the Data Dictionary component.
There is more information in the RBuilder.hlp file on using the Data
Dictionary.
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com