|
| Hi:
I've inherited a project that uses Crystal32.ocx v 8.0.0.4 for thousands of
reports. I'm doing the VB 6 and someone else is doing the reports. To
simplify the interface and minimize handshaking problems, I want to just
pass parameters and let the report writer worry about the SQL (Sql Server).
When he runs in the Crystal environment he should be prompted for the
paramters. When the report is called from VB, the parameters are passed and
should not be prompted. The code I'm doing this with is like the following:
MdiSect.crw.ParameterFields(0) = "Begin;Date(" & Format(txtBeg,
"yyyy,mm,dd") & ");true"
MdiSect.crw.ParameterFields(1) = "End;Date(" & Format(txtEnd,
"yyyy,mm,dd") & ");true"
MdiSect.crw.ParameterFields(2) = "SelectKey;ABCDE;true"
I understand the "true" is supposed to remove the prompt. Instead it
removes the data and leaves the prompt with default blank values. When I
use "false", I am prompted with the correct default values.
1. Is there some Crystal setting that will make this work properly, i.e. no
prompt if "true"?
2. Is there a slightly newer build of Crystal32.ocx that doesn't have this
problem? The customer is not anxious to upgrade if there are major changes.
Remember there are thousands of .rpts and thousands of .rpt calls from VB.
3. I understand that the ocx goes away in later versions. Will 8.5 work and
solve the problem without requiring changes in the .rpts or the VB6? If so,
is it still possible to buy that upgrade?
Thanks in advance,
Terry
|
|