CReports, 'viDate' structure wrong?

[JoelMcNary]

I'm using the C api library and the
viDate structure in and around these
two calls:

Call PEGetNthParameterCurrentValue Returns
Call PEAddParameterCurrentValue

Both these calls use a data structure
called 'viDate' which is defined to
be an array of 3 short ints. We load
the ints with valid YY MM DD values,
and we get an invalid value/overflow
error on some of them (mostly current
dates). It seems 'viDate' is not documented
properly - any one know the correct use
of 'viDate' for date loading onto a report?

.

 

[vidru]

This is the only reference to viDate I could find on the Crystal support site:

http://support.businessobjects.com/library/kbase/articles/c2000289.asp

Looks like viDate is an array with 3 elements: year, month, and day.

-dave

 

[JoelMcNary]

... yes ... we know this
is what it says, we also
know this is NOT the way
it works!

 

[vidru]

If you're passing a two digit year, change it to four digits.

-dave

 

[JoelMcNary]

... thanks for your attentiveness.
We are entering years of all types -
the same condition applies: the
output is not as described. Have you
actually implemented this
particular API, or are you giving
us advice after reading the
documentation?

We are sending it three valid ints
(three little pigs?) - we are
getting garbage output. The problem
isn't with our input in the sense
that we are obeying the description.

Have you tried this API yourself?

thanks.

 

[vidru]

I've only tried it using their VB API sample apps, not with C or C++.

Sorry, mang... can't help you.

Good luck,

-dave