Crystal Reports - 没有为此表、查询或过程返回行集 - 崩溃!
我正在使用 Crystal Reports 8.0.1.0 并将 OLEDB 连接设置为“最喜欢的”。 我们有几个针对数据库上的一些存储过程运行的报告。 我们的数据库是一个 SQLExpress 2005 命名实例。
其中一份报告涉及平衡,即我们必须为特定公司或一组公司提供平衡报告。
然而,客户特别要求我们有一个单独的部分作为特定经济账户类型的最后一个部分,为了做到这一点,我们必须将这一部分与其他部分分开,而其他部分则使用两个并行子报告来显示。
因此,我们的结构应如下所示:
GENERAL HEADING
PATRIMONIAL STATE
...data...
ECONOMIC COUNTS
...data...
THIRD-PARTY EFFECTS
...data...
总标题下方的前两个部分是通过两个并行子报表实现的,因此现在我们必须显示第三部分。 到现在为止已经清楚了吗? 好吧,您可能很清楚,CR 子报告要求您设置数据库位置,无论您是否已经为主报告设置了数据库位置。 然而,问题是,如果我尝试设置指向我们的存储过程的位置(它返回余额报告的全部数据),第一次它将在主题中显示消息,并且再来第二次,但这一次也会崩溃。 我们的存储过程有一个参数,并且之前的两个子报告(并行的子报告)都设置为相同的 SP 并且运行完美。
这次崩溃使我无法完成第三部分,而且我几乎不知道解决手头问题的最佳方法是什么。
有什么想法/建议吗?
我很高兴收到您的答案,我希望我的问题足够清楚(如果需要的话,我非常愿意进一步深入研究以进行澄清)。
非常感谢您抽出时间,
安德里亚·雷蒙迪
I am using Crystal Reports 8.0.1.0 and have an OLEDB connection set as "favourite".
We have several reports being run against a few stored procedures on the database.
Our database is an SQLExpress 2005 named instance.
One of the reports deals with balance, i.e. we have to provide a balance report for a specific company or set of companies.
The customer, however, has specifically asked us to have a separate section to be the last one for a specific economic account typology and in order to do this, we have to separate this one from the others which are instead displayed using two parallel subreports.
Hence our structure should be like follows:
GENERAL HEADING
PATRIMONIAL STATE
...data...
ECONOMIC COUNTS
...data...
THIRD-PARTY EFFECTS
...data...
The first two sections below the general heading are achieved with two parallel subreports, so now we have to display the third section.
Is it clear up to now? Well, as you may well be aware, CR subreports require you to set the database location, regardless if you have set one up already for main report.
The problem, however, is that if I try to set the location pointing to our stored procedure(which returns ALL the data for the balance report), the first time it will display the message in subject, and the second time again, but this time it'll also crash.
Our stored procedure has a parameter and both previous subreports(the ones in parallel) are set to the same SP and are working flawlessly.
This crash makes it impossible for me to work on the third section and I'm pretty much at loss as to what would be the best approach to solve the issue at hand.
Any ideas/suggestions?
I would love to receive your answers and I hope my problem was clear enough(I'm very willing to further delve into it for clarification if ever needed).
Thank you so much for your time,
Andrea Raimondi
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
天哪...将连接从 OLEDB 更改为 SQLServer 它可以正确获取行集并且不会崩溃!
我无言以对。
安德鲁
Geez... changing the connection from OLEDB to SQLServer it correctly fetches the rowset and doesn't crash!
I am speechless.
Andrew