Wierdness going on with End User Reporting SQL7 with ADO

rbuser

I have something strange going on with 'End User Reporting' sample. First,
let me say, I've implemented a 'Report Explorer' subsystem in 4 previous
applications. This is the first time though I've implemented it using D7
and the latest version of Report Builder. I'm having mega problems and I'll
be darned if I traced Digital Metaphor's code for 6 hrs to no avail. Here's
the problem.

I have copied a plain ol' vanilla 'TmyEndUserSolution' class from the RB
demo's library. I have nothing special in that class like I've done in the
past. Added that unit to my project. The following references an
TADOConnection object that I have.
tblFolder.Connection,
tblItem.Connection,
tblTables.Connection,
tblFields.Connection,
tblJoins.Connection
ppDesigner1.DataSettings.DatabaseName aslo references it, &
ppDataDictionary1.Datasettings.DatabaseName references it.

All pipelines are configured and field names match what I have in the
database.

When I run my application and launch the Report Explorer Form, I see all of
my reports, folders, etc. (a good thing), I can go to 'design' view for
that report and see the data queries and their fields (a good thing), but
HERE's THE PROBLEM, when I run the report OR invoke
ppReportExplorer.LoadReport...the report wants to use some default
ADOConnection associated with that report. I get prompted for a
username/password combination (someetimes I get a dlg box consecutively a
few dozen times...like it's iterating through some list). Then I get some
datasource missing error, I can't think of what exactly it errors with b/c
it's so hard to get past all those password prompts.

Anyone have any thoughts? I'm in desparate need...project is coming to an
end and this...this is baffling me. I'm sure I'm missing something simple
like some goofy property setting or something.

Thanks in advance...

nicocizik

Hello,

When creating your templates to be used with ADO, you need to define an
ADOConnection component that exists on your applicaton form or data module,
which in turn connects to your SQL Server database using a connection string
you create (as well as sets the connection options such as showing the login
prompt). If you do not define this connection, ReportBuilder will try to
create a default ADOConnection which in your case seems to be working
partially but is not what you are after. Please see the SQL Server 7/ADO
end user demo application and readme.doc files on how to set this connection
up as it is a little different than BDE.

--

rbuser

thanks Nico...I'll look at that. I don't think I have even created a
template; maybe it defaults to one of your templates or something. Is this
new functionality? We used v6.02 for the past several years and I don't
think I ever did that for the past several years/projects?!? I don't know
maybe I did.

Thanks again,
Randy

nicocizik

Hello,

I'm sorry, I may have been a little unclear. In ReportBuilder, all reports
are essentially a template. Inside the Report object, instructions are
saved that define the report layout. These instructions can then be saved
as a separate file or a template. In my previous answer, if you replace the
word "Template" with "Report Object" it may make more sense. Sorry for the
confusion.

--