Crystal Report VerifyDatabase不工作 [英] Crystal Report VerifyDatabase not working
问题描述
我有一个针对dev数据库设计的Crystal报表。当我将它加载到实时系统中时，我需要它运行一个不同但等效的数据库。通常我只是通过一些代码在C＃中运行报告设置连接信息，参数和调用VerifyDatabase在报告和子报告，它一切正常。
I have a Crystal Report that was designed against a dev database. When I load it into the live system I need it to run a different but equivalent database. Normally I just run reports through some code in C# that sets the connection info, parameters and calls VerifyDatabase on the report and subreports and it all works well.
在一个特定的报告中，这不工作，似乎没有验证任何东西，报告崩溃时出现错误字段名称不知道的子报告。使用此报告如果我在Crystal Reports应用程序中针对实时数据库手动验证它，那么它一切正常。
In one particular report this doesn't work though and doesn't seem to verify anything and the report crashes with an error 'The field name is not known' in one of the sub reports. With this report if I manually verify it in the Crystal Reports application against the live database then it all works fine.
所以问题是，在Crystal应用程序中验证数据库函数是否有什么不同，我应该在除设置连接信息，参数和调用VerifyDatabase方法之外的代码？
So the question is, is there anything different that Verify Database function in the Crystal application does that I should do in code other than set connection info, parameters and call VerifyDatabase method?
编辑：有关我尝试的更多信息
Some more info on what I tried
- 手动验证针对此数据库的报告（与实时数据库具有完全相同的结构）
- 将报表载入实时系统并运行。
错误仍然出现。
推荐答案
这听起来像是两个版本的Crystal和他们的能力之间的混乱。 dotNET 2008附带的版本是VS2008的Crystal Reports Basic，伪装为Crystal 10.5（不作为独立产品存在）。但是如果你指的是由Visual Studio IDE外部自行开发的独立报表，那么这将是一个不同版本的Crystal，但有一些差异。我想说，这个报告是在不同版本的Crystal中创建的，其他人，并且验证代码中有一些功能，10.5无法识别。
如果您有Crystal的独立版本（需要为Crystal Reports 2008或早期版本的Developer Edition），请使用这，以确保您使用相同的Crystal版本该应用程序在报告开发。
It sounds like a confusion between two versions of Crystal and their capabilities. The version that comes with dotNET 2008 is Crystal Reports Basic for VS2008, masquerading as Crystal 10.5 (which doesn't exist as a standalone product). But if you're referring to standalone reports developed by themselves outside of the Visual Studio IDE, then this will be a different version of Crystal with some differences in capability. I'd say this report was created in a different version of Crystal to the others, and that the Verify within the code is coming across some feature that 10.5 can't recognise. If you have a standalone version of Crystal (which will need to be either Crystal Reports 2008, or a Developer edition of an earlier version), use this to make sure you're using the same Crystal version in the app as in in report development.
这篇关于Crystal Report VerifyDatabase不工作的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
