Yep, I'd call it "flaky"! How's this for a weird one.....
Running ITSM 6:
On my PC, running Crystal 9 Advanced at patch level 9.2.3.1368, I was
not able to create a report running against SHRR-CHG-ChangeTaskJoin.
When trying to add the form to my report, I got a Crystal Engine Driver
error 220: Out of range or something similar. I narrowed this down to
the CHG:Task form - it failed with the same error, but I was able to add
other forms into my report without issue (including CHG:Change &
HPD:HelpDesk).
On another PC running Crystal 9 Advanced unpatched, I was able to create
the report successfully against SHRR-CHG-ChangeTaskJoin. No errors were
reported.
After the report was created, I was able to run it within Crystal
successfully on both PC's, so the Crystal patch level didn't seem to
stop the report running. However, on my PC with the patched Crystal
version, when I tried to "Verify Database" I got the same driver error
so something was still a little weird...
The next strange thing is that when I tried testing the report in the
User Tool (6.3 patch 03), it crashed my client - every single time. We
had about six testers experience the exact same issue, the report didn't
work for anyone.
So, back to the drawing board. I knew it was CHG:Task causing the issue,
so I systematically removed from the join form each field that came from
CHG:Task. What I found was that if I removed both the "Planned Duration"
and "Actual Duration" fields from the join, I was able to verify the
database on my PC using the patched Crystal version successfully.
Not only that, but once I'd verified the report and saved it on my PC,
it tested and ran perfectly from the User Tool.
Very odd - the fields in question that I had removed from the join were
both Real fields, but the CHG:Change form has some real fields on it as
well that were still present on the join and not causing issues. None of
these fields were actually being used by my report.
Flaky? I think so.....
Matt
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Axton
Sent: Thursday, 16 March 2006 1:09 PM
To: arslist@ARSLIST.ORG
Subject: Re: AR System ODBC Driver and SCRIBE
Compatability issues with ARUser and CR Designer versions/patch levels
(ever tried patching your CR Designer or CR Web Compoent Server?)
Problems with using reporting programs other than CR using the ARODBC
driver. (Can't off the top of my head remember the programs I used in
the past that had issues)
Formula reliability inconsistencies when generating reports using the
ARDBC driver.
Not relevant to this conv., but report design inconsistencies in reports
from ITSM version to version.
Call it what you want.
Axton Grams
On 3/15/06, Carey Matthew Black
wrote:
> Axton,
>
> Flaky? Really? You have had problems with it working, not working,
> and working again for some unknown reason?
>
> Limited...yes.. by Remedy design. (AKA: Working as designed) However,
> I have not had problems with it being "Flaky".
>
> --
> Carey Matthew Black
> Remedy Skilled Professional (RSP)
> ARS = Action Request System(Remedy)
>
> Solution = People + Process + Tools
> Fast, Accurate, Cheap.... Pick two.
> Never ascribe to malice, that which can be explained by incompetence.
>
>
>
> On 3/15/06, Axton wrote:
> > Do keep in mind that Remedy's ARODBC driver is flaky at best.
> > Supported ODBC call types are extremely limited.
> >
> > Axton Grams
>
>
> UNSUBSCRIBE or access ARSlist Archives at
> http://www.ARSLIST.org
>
UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org
**********************************************************************
The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorised. If you have received this communication in error, please notify us immediately by return e-mail with the subject heading "Received in error" or telephone +61 2 93357000, then delete the email and destroy any copies of it. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any opinions or advice contained in this e-mail are subject to the terms and conditions expressed in the governing KPMG client engagement letter. Opinions, conclusions and other information in this e-mail and any attachments that do not relate to the official business of the firm are neither given nor endorsed by it.
KPMG cannot guarantee that e-mail communications are secure or error-free, as information could be intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or contain viruses.
KPMG, an Australian partnership, is part of the KPMG International network. KPMG International is a Swiss cooperative that serves as a coordinating entity for a network of independent firms operating under the KPMG name. KPMG International provides no services to clients. Each member firm of KPMG International is a legally distinct and separate entity and each describes itself as such.
Liability limited by a scheme approved under Professional Standards Legislation.
This footnote also confirms that this e-mail message has been swept by MIMEsweeper for the presence of computer viruses. See www.mimesweeper.com for more information.
**********************************************************************
UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org
Previous Topic
Index