Re: Crystal Reports 5.0 (32-Bit) and Forte 2.0H16 on NT3.51

Question

Dear Silke,
Crystal's default for identifying a table in the report design is
<schema>.<table>. You can change that by going to the Database Location menu
item and cutting the schema prefix off. You should do that for every table in
the report. The PESetNthTableLogOnInfo function will, I believe, not change
the schema prefix of a table, since it assumes you really want that schema,
i.e., as an override. Also, if you are using the propagateAcrossAllTables
feature of the function make sure that every table has the schema prefix cut
off, otherwise those tables will be skipped, since the propagate feature applies
to all other similar tables only. For example, some of the tables could be
Sybase, etc.
I believe you can change the default behaviour of the CR Report Designer in the
File->Preferences menu, so that when reports are designed the schema prefix is
not automatically attached.
I have compiled some guidelines on designing reports to make them work properly
with Forte. I will try to send them to you next week. Crystal Reports and its
C API are a good product, and you will get good performance once the report
design is set up properly.
Yours very sincerely, John Hodgson.
Schulte, Silke (DVD) wrote:
The problem seems to be, that Crystal stores the database name in the
report. If you want to change the database you have to develop your
report new, although you give the connection-information via the API.
The hotline from Crystal told us, when using subreports you have to use
the PESetNthTableLogOnInfo and to go through all the subreports and
change the connect-string.
Our experience is, you have to do both: change the report and call the
other function for the subreports.
Thank you very much for all the tips.
Regards
Silke Schulte
Union-Investment, Frankfurt / Main, Germany
e-mail: [email protected]
From: Ajith Kallambella M[SMTP:[email protected]]
Sent: Mittwoch, 23. September 1998 15:17
To: [email protected]; ForteUsers; [email protected]
Subject: RE: Crystal Reports 5.0 (32-Bit) and Forte 2.0H16 on NT
3.51
Hi There,
Crystal reports stores Database name as a hard-coded
value in the
report template. So if you have to use an other
database, you will
have to open the report template and modify the
database name. I
think this is why you are getting Crystal API error.
Hope this helps!
Ajith Kallambella M
Forte systems Engineer,
International Business Corporation.
Hello,
I wonder if we have a similar problem.
We are using Crystal Reports 5 and Forte 3.0.F.2. For
the interface
between Forte and Crystal we have in Forte a Lib using
C-wrappering to
the C-API of Crystal.
We have developed a report on a database in our
development-environment. This report comes up with data
and works
correct. It's no different if we have saved the report
in Crystal with
data or without.
If we want to use the same report on another database
in our
test-environment the window from crystal reports comes
up and when
starting there is an error from the Crystal API
function.
Both environments use the same version of an Oracle
Database and are on
Open VMS. The client for the test is in this case
always the same.
From the C-API we use the method PEStartPrintJob after
we have specified
the rest for the report.
Is there a possibility that this is the same error you
mentioned? Or do
you have any other ideas?
Any help is appreciated.
Regards
Silke Schulte
Union-Investment Frankfurt (Germany)
email: [email protected]
From: Katie Carty[SMTP:[email protected]]
Reply To: Katie Carty
Sent: Montag, 21. September 1998 19:14
To: 'Tim Hagemann'; [email protected]
Subject: RE: Crystal Reports 5.0 (32-Bit) and Forte2.0H16 on NT
3.51
Tim,
You need to upgrade to CrystalReports 6.0. There isa bug in the
interaction between Forte and CrystalReports 5.0 (Idon't know on
which side the bug resides, but I think that it is onthe Crystal end,
since the problem occurs both through C-wrapperingand OLE
interaction), which does not allow you to invoke thePrintReport
method unless you have saved data with the report.
As far as I know, there is no workaround, and theonly solution is to
upgrade to CrystalReports 6.0.
FYI, there is no ActiveX control supplied withCrystalReports 5.0 -
you are actually using standard OLE integration.
Hope this helps...
Regards,
-Katie
-----Original Message-----
From: Tim Hagemann [SMTP:[email protected]]
Sent: Monday, September 21, 1998 11:27 AM
To: [email protected]
Subject: Crystal Reports 5.0 (32-Bit) and Forte2.0H16 on NT 3.51
Hi Forte-User !
We got a big problem here using the crystal active-xcontrol. On my
windows-nt 4.0 machine (with
crystal reports installed completely) all works well.On our test
machine (with only the crystal ActiveX
installed), the Forte runtime shuts down afterinvoking a special
method of the ocx (PrintReport).
The cause for shutting down (no stacktrace orsomething like that) is
a generated c++ exception in crystal -
but we don't know the cause of this exception.
Has anyone made the control work under nt 3.51 ? Doesanybody know
(exactly) what dll's we'll have
to use ?
TIA,
Tim Hagemann
Tim Hagemann
Ascom GmbH Email:
[email protected]
Charlottenburger Allee 61 Phone: [phone]
D-52068 Aachen Fax: [phone]
>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Answer 1

Dear Silke,
Crystal's default for identifying a table in the report design is
<schema>.<table>. You can change that by going to the Database Location menu
item and cutting the schema prefix off. You should do that for every table in
the report. The PESetNthTableLogOnInfo function will, I believe, not change
the schema prefix of a table, since it assumes you really want that schema,
i.e., as an override. Also, if you are using the propagateAcrossAllTables
feature of the function make sure that every table has the schema prefix cut
off, otherwise those tables will be skipped, since the propagate feature applies
to all other similar tables only. For example, some of the tables could be
Sybase, etc.
I believe you can change the default behaviour of the CR Report Designer in the
File->Preferences menu, so that when reports are designed the schema prefix is
not automatically attached.
I have compiled some guidelines on designing reports to make them work properly
with Forte. I will try to send them to you next week. Crystal Reports and its
C API are a good product, and you will get good performance once the report
design is set up properly.
Yours very sincerely, John Hodgson.
Schulte, Silke (DVD) wrote:
The problem seems to be, that Crystal stores the database name in the
report. If you want to change the database you have to develop your
report new, although you give the connection-information via the API.
The hotline from Crystal told us, when using subreports you have to use
the PESetNthTableLogOnInfo and to go through all the subreports and
change the connect-string.
Our experience is, you have to do both: change the report and call the
other function for the subreports.
Thank you very much for all the tips.
Regards
Silke Schulte
Union-Investment, Frankfurt / Main, Germany
e-mail: [email protected]
From: Ajith Kallambella M[SMTP:[email protected]]
Sent: Mittwoch, 23. September 1998 15:17
To: [email protected]; ForteUsers; [email protected]
Subject: RE: Crystal Reports 5.0 (32-Bit) and Forte 2.0H16 on NT
3.51
Hi There,
Crystal reports stores Database name as a hard-coded
value in the
report template. So if you have to use an other
database, you will
have to open the report template and modify the
database name. I
think this is why you are getting Crystal API error.
Hope this helps!
Ajith Kallambella M
Forte systems Engineer,
International Business Corporation.
Hello,
I wonder if we have a similar problem.
We are using Crystal Reports 5 and Forte 3.0.F.2. For
the interface
between Forte and Crystal we have in Forte a Lib using
C-wrappering to
the C-API of Crystal.
We have developed a report on a database in our
development-environment. This report comes up with data
and works
correct. It's no different if we have saved the report
in Crystal with
data or without.
If we want to use the same report on another database
in our
test-environment the window from crystal reports comes
up and when
starting there is an error from the Crystal API
function.
Both environments use the same version of an Oracle
Database and are on
Open VMS. The client for the test is in this case
always the same.
From the C-API we use the method PEStartPrintJob after
we have specified
the rest for the report.
Is there a possibility that this is the same error you
mentioned? Or do
you have any other ideas?
Any help is appreciated.
Regards
Silke Schulte
Union-Investment Frankfurt (Germany)
email: [email protected]
From: Katie Carty[SMTP:[email protected]]
Reply To: Katie Carty
Sent: Montag, 21. September 1998 19:14
To: 'Tim Hagemann'; [email protected]
Subject: RE: Crystal Reports 5.0 (32-Bit) and Forte2.0H16 on NT
3.51
Tim,
You need to upgrade to CrystalReports 6.0. There isa bug in the
interaction between Forte and CrystalReports 5.0 (Idon't know on
which side the bug resides, but I think that it is onthe Crystal end,
since the problem occurs both through C-wrapperingand OLE
interaction), which does not allow you to invoke thePrintReport
method unless you have saved data with the report.
As far as I know, there is no workaround, and theonly solution is to
upgrade to CrystalReports 6.0.
FYI, there is no ActiveX control supplied withCrystalReports 5.0 -
you are actually using standard OLE integration.
Hope this helps...
Regards,
-Katie
-----Original Message-----
From: Tim Hagemann [SMTP:[email protected]]
Sent: Monday, September 21, 1998 11:27 AM
To: [email protected]
Subject: Crystal Reports 5.0 (32-Bit) and Forte2.0H16 on NT 3.51
Hi Forte-User !
We got a big problem here using the crystal active-xcontrol. On my
windows-nt 4.0 machine (with
crystal reports installed completely) all works well.On our test
machine (with only the crystal ActiveX
installed), the Forte runtime shuts down afterinvoking a special
method of the ocx (PrintReport).
The cause for shutting down (no stacktrace orsomething like that) is
a generated c++ exception in crystal -
but we don't know the cause of this exception.
Has anyone made the control work under nt 3.51 ? Doesanybody know
(exactly) what dll's we'll have
to use ?
TIA,
Tim Hagemann
Tim Hagemann
Ascom GmbH Email:
[email protected]
Charlottenburger Allee 61 Phone: [phone]
D-52068 Aachen Fax: [phone]
>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>