Still waiting for an answer on defaultConnection

rbuser

Hi,
I posted on this group a couple of weeks ago about a defaultConnection
problem when running reports designed in a different application to the
destination application.
An initial response told me to make sure that all the tables and fields
were present and identical, and that new views could be created using
them. This is the case, as I replied, however I have not received any
further information since then. I need this information as it is
crippling one of my current development efforts.
As a reminder, the case is simple: I am taking report files developed in
application A and putting them as menu items under application B. In
both application the exact same ADO connection string connects the
reports to the exact same database. Only when I try to run the reports
in application B it obstinately tells me that it is trying to open a
default ADO connection which never works.
Please, I need a solution to this bug.
Thank you
Philippe

digitalmetaphors

The DADE plugin will create a default ADOConnection when it cannot find the
connection. Make sure that the Designer.Datasettings are correct and that
you can create a new dataview at runtime (meaning that you can connect to
the ADOConnection). Then save one of the App A reports as an ascii tempalte
(Report.Template.Format) to see the objects stored in it. It should list the
dataview objects. There you can see the database name (ADOConnection name)
that the dataview is trying to connect to when you load it in App B. This is
going to be the name of the ADOConnection it expects to find, otherwise, a
default ADOConnection will be created.


Cheers,

Jim Bennett
Digital Metaphors