Problems with Auto Joins, MSSQL 2000 and ADO

rbuser

I am using Report builder 7.0.1 and Delphi 6.


I have clients using one of three database Oracle 8i, Interbase 5.5, and
MSSQL 7.0 and 2000. My End-user Reports must be able to support all
three of these databases. To make this work I have had to do the following:

When the client is an Interbase client I am connecting with the BDE,
TTables and having no issues.

The BDE did not work for Oracle or MSSQL. The Oracle problems were
solved by checking if the database is Oracle then use DBExpress. This
is now also working.

Neither of these two options has worked for MSSQL. I started to use ADO
and ADOTables (like the demo that is shipped with report builder ) and I
am still having trouble with the Auto-Joins (nothing shows up bolded)
If I change the connection from an ADO connection to an BDE connection
the joins work but I have issues with adding new folders in the Report
Explorer.

When I take the ADO sample program that comes with Report Builder and
set the database connection to point to my database and tables, set
Auto-join to True and set the UseDataDictionary property on the
ppDesigner to true, I have the same issues with Auto-Joins. They do not
appear to be working. Nothing is bolded I choose the second table and it
immediately suggests a join using the same field names and totally
ignores the join I have defined.

Any help is greatly appreciated

Thanks,

Rebecca

digitalmetaphors

We recommend steering away from the BDE if at all possible. Search the web
for known issues with the BDE. I remember an article a while back in the
Delphi Mag which talks about resource leaks with the session. There is a
listing of BDE alternatives on our website along with the different DADE
plugins available for third party data access components.
www.digital-metaphors.com

First, try to get SQL Server working correctly using our end user demo using
ADO. It is working correctly here for us. Make sure the AutoJoin is true on
the dictionary component. Verify that UseDataDictionary is true on the
designer's DataSettings property. Also, make sure you only have one set of
database tables for the data dictionary. Our end user demos by default is
set to not use the data dictionary on the DataSettings of the designer.

There is a topic in the help file called troubleshooting where we list a
table of the known data connectivity for different databases. You'll see
that we have not been able to get the BDE to connect to Oracle. For Oracle,
you may want to check out DOA (Direct Oracle Access)- it is a very popular
and easy to use VCL component.


Cheers,

Jim Bennett
Digital Metaphors