Why does RecordSelectionFormula suddenly reject my formula? - vb6

I have a VB6 application using Crystal Reports XI.
After almost two years suddenly I cannot set RecordSelectionFormula anymore. The error message says, that Basic syntax is not allowed in record selection formula.
The formula is {article.id} = 1234.
I've tripple checked that formula. It works fine in the Crystal Reports designer, but even if I save that formula and change it at runtime to {article.id} = 1235 I get the same error message. Also there's no reason why this worked the whole time and suddenly not.
After googling I find that a few users have the same problem, but since Crystal Reports 11 and VB6 are somewhat antiquated, nobody seems to have solution, except updating to a newer versions of Crystal Reports or Visual Basic.

Are you now running on Vista? Crystal XI has known issues with it and there's no patch. However, Crystal XI Release 2 is a free download for existing users of Crystal Reports XI and combined with the subsequent service packs should solve some issues :
http://resources.businessobjects.com/support/additional_downloads/service_packs/crxir2.asp
There is also this, extracted from a google cache of an old CR knowledge base entry :
KBase Article ID:c2018734
Article refers to:Crystal Reports XI
Symptom
When a Report Designer Component (RDC)
XI web or Windows application passes
a record selection formula to a report
at run time, the following error
message appears:
"Basic syntax is not supported in
group/record selection formula"
Why does this error message appear and
how do you resolve it? Resolution
The error message appears after an RDC
application has been upgraded from a
previous version. As a result, the
record selection formula is being
interpreted as Basic syntax, even if
it is not Basic syntax.
To resolve the error message, add
these lines of code to your
application so that they are executed
before the record selection formula
is passed to the report:
' report is the name of the 'Report'
object
' sets the record selection formula to
be interpreted as Crystal syntax
report.FormulaSyntax = 0 ' Use
crCrystalSyntaxFormula value

Related

Crystal Report Engine error

i am stuck with a problem regarding Crystal Report 13. I am working on Visual Studio 2013 developing Web Application.
Previously i've developed reports and those were working fine but after some time on web page crystal report viewer stop rendering. I tried to resolve the issue by suggestions on different forums where i need to add reference of Crystal Report 13 files in my Web.Config. After all changes the problem was not resolved. Than people suggested me to re-install redistribution package of crystal report 13, i've done the same thing now there is a new problem which is quite different. Whenever i am trying to open page it shows following error:
Server Error in '/Abcd' Application.
The document has not been opened.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Runtime.InteropServices.COMException: The document has not been opened.
I've tried many forums and different suggestions but all seems useless, i've check the appropriate rights even try after giving full rights but still at same position.
I've found the alternative solution, before i was using 13.0.21 redistribution package which was using registry dlls version 13.0.2000.0, i was facing two problems using that particular version.
1. Unable to edit rpt file, whenever i tried to open it an error appear on screen that The operations is failed or unable to complete operation (something like that i don't know exactly what the error is but the summary is this)
2. When i try to open Crystal report viewer during execution, i've come up with error which i posted earlier.
What i have done for the resolution, that i've download Crystal report developer version 13.0.21 and install it with "Run as Administrator" because i creates some entries in your registry of windows, keep in your mind to close VS during installation. After successful installation both problems are solved but u need to change the dlls version in your code from 13.0.2000.0 to 13.0.3500.0

Open-XML-SDK not reporting errors in documents that Word fails to open

When opening a test Word document I see the following Error:
However, when validating the same document using "Open XML SDK 2.5 Productivity Tool for Microsoft Office", the error is not shown at all.
Thinking this may be due to 2.5 being a bit old, I cloned and compiled the latest Open-XML-SDK GIT repository and then ran a programatic validation. Still the error remains undetected.
This validation inconsistency is a real problem for me so if anyone can point me to a tool / method that validates in a a way synonymous with the way Word validates I would greatly appreciate it!

SonarQube 6.0 Link to code for issues not working

We have an issue since our upgrade to SonarQube 6.0 that on the issues page the link icon or the right arrow icon no longer link to the code.
In this case clicking either link takes you to another (smaller) list of issues.
This is not the case for all issues, the only difference I can spot is that on the problem issues the filename and line number are not shown. checking in the database and in the issues table the 'line' column is also null.
We are using SonarQube 6.0 with C# plugin 5.3.2 - Analysis is triggered by TFS2015 Update 3
Many thanks in advance for any ideas/advice.
Following Teryk's response I manage fine tune my investigation. It turns out that it is cased by the MSBUILD output which does not include a filename or line for certain CA warning is Microsoft.Design and Microsoft.Naming, e.g. CA1024, CA1040, CA1704, CA1716, thus:
3>MSBUILD : warning CA1040: Microsoft.Design : Define a custom attribute to replace 'ITierRepository'.
When this happens the issue is recorded against the solution but obviously cannot be assign to a specific file and the line not identified.
Having found that I was quick able to find the article which discusses the same issue:
https://groups.google.com/d/topic/sonarqube/UDIIjWbCGjs
It is caused by the fact that FxCop is not able find source for the issue as described here:
https://blogs.msdn.microsoft.com/codeanalysis/2007/05/12/faq-why-is-file-and-line-information-available-for-some-warnings-in-fxcop-but-not-for-others/
It apparently relates to changes to FxCop reporting that were introduced in v5.2 of the C# plugin which was also deployed at the same time as upgrading to SQ 6.0

How to Validate a Cognos report in debug mode ( element-by-element or step-by-step)

We recently migrated from Cognos 10.1.1 to Cognos 10.2.1.1 ( 10.2.1 plus Fix pack1) . Some of our existing reports fail validation now.
From the cogserver.log file , it looks like the BIBUS Process is Crashing on validating the report.
We are working with IBM tech support via a PMR .
Wanted to try if someone here knows if it is possible to Validate a report step by step so that I can get some information or some logs on what element in our report is exactly causing the issue? i.e. Is it possible to do the report validation in a debug mode somehow?
Oh, what a wonderful feature that would be, but to my knowledge nothing like that exists at all. You could try setting the logging on your dispatcher(s) to the maximum to see if you can get any more informative errors.
I would start by trying to view the tabular data for each query individually. If you can identify which query (or queries) are causing your problems, then you can just remove items from the query until it doesn't fail, at which point you should have a pretty good idea of what the source of the problem is.
If that doesn't work, I would just start ripping major chunks of the report out and seeing you can get it to run. For example, if you have a report with 4 charts, delete half of them and try your report. Revert back to the original report, and delete the other half. Get it to work, and then start removing stuff from the half that fails until you can narrow it down to your problem.
It's kind of slow, but these approaches have always worked for me.
On a side note, we're about to make the same upgrade, I'd be interested in hearing what you learn.
EDIT:
Oh, forgot. Make sure you disable DQM and test your reports that way, if you haven't.
Unfortunately, there's no way to debug step by step. Finally got the Core dumps for the crashes, sent them over to IBM Folks ; and they identified it as a known bug in 10.2.1.1. So now we are at 10.2.1.2 (applied Fix pack 2) which solves the issue.

Method or Data Member not Found Error?

Using VB 6 and Crystal Report 9
I want to display an output in the crystal report. Last week I used VB 6 and Crystal Report 8.5, it was worked fine, but last day I reinstall my Windows XP, VB 6 and crystal report 9. After that While executing the code it showing “Method or Data Member not Found Error”. I checked the Component and References. It is also same before I used.
Code.
CR.ParameterFields(1)
…….
CR – Picture Box
Not accepting this lines,
CR.ParameterFields
CR.DataFiles
CR.ReportFileName
CR.Action
System File was changed or …? What wrong it is?
How to solve this problem? Can any one help me
It would seem a class/method has changed between the two versions of Crystal Reports. Suggest you check the documentation for the specifics.

Resources