By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,515 Members | 1,110 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,515 IT Pros & Developers. It's quick & easy.

CallByName - Trying to understand.

P: n/a
Hi,

We had real bad problems with reports being printed wrong (active reports
..net 2.0), which we tracked down to being because before we printed the
report we used CallByName to READ properties from the Business Object that
the report was based on.

When I replaced the old CallByName's call with a small Reflection code
instead, the problem went away.

Now Im just curious what caused it, It seems that if you use CallByName
(even if its just Get) it changes the object somehow, not "visiable" but
enough for the report to go bad.

It was actually depending of how much time elaped between the CallByName
call and the report printing, if you let enough time go by (above 10
seconds) there was no problem.

Anyone seen this behavior before?
(Please note that we already found the fix for it, im just curious why it
happens)
Apr 3 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a

Fredrik Melin wrote:
<snip>
We had real bad problems with reports being printed wrong (active reports
.net 2.0), which we tracked down to being because before we printed the
report we used CallByName to READ properties from the Business Object that
the report was based on.

When I replaced the old CallByName's call with a small Reflection code
instead, the problem went away.
<snip> Anyone seen this behavior before?
(Please note that we already found the fix for it, im just curious why it
happens)


it would help if you posted the code that was giving you wrong results
and the new code that corrected the issue.

Regards,

Branco.

Apr 3 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.