Jase,
 
I think I had a similar problem like yours long ago, my memory is a bit
hazy.  I think what the problem ended up being was specific records
missing a history.  So when you attempted to report on those incidents,
it choked.  I recommend that you run the search in the usertool, and
then press control H as you're scanning through the records to see if
any come up strangely or if you get an error.  Alternately if you're not
finding any damage incidents, I suggest trying the Excel pointed to a
specific incident (one that you know IS good) and see if it'll display.
 
Hope this ends up being helpful.
 
 
Ben Cantatore
Remedy Manager
(914) 457-6209
 
Emerging Health IT
3 Odell Plaza
Yonkers, New York 10701


>>> [EMAIL PROTECTED] 05/20/08 10:30 AM >>>

** I am not using 7.1 but am using 7.0. My ARODBC version is 7.00.01.07
and I do not have any issues using the status history columns in queries
from Excel. Not sure if 7.1 uses the same ODBC version.

HTH

On Mon, May 19, 2008 at 4:44 PM, Jase Brandon <[EMAIL PROTECTED]>
wrote:
** Hello All,
 
I have a user writing corporate reports using Excel/Remedy ARODBC to
connect to prod dbase. (I know, I laughed too) :)
All was fine until last week, when absolutely nothing changed (as far
as I know).
 
Using Excel and his Remedy ARODBC login, he is now unable to query
HPD:HelpDesk for 
Status.History. If he queries on any other field, no problemo. 
If he adds Status.History.New, etc.. to the query, it bombs and returns
the message.
"Cannot open catalog, message number = 94, servername"
 
Has anyone else seen this?
I get the same result when using my ARODBC as well.
I have verified running the exact same query through SQL Query Analyzer
and it works flawlessly.
I can query H1024 with no problem, T1024 also.
Please see his below excel query.
 
This one works:
SELECT "HPD:Help-Desk"."Incident-Number"
FROM "HPD:Help-Desk" "HPD:Help-Desk"
WHERE ("HPD:Help-Desk"."Incident-Number" Is Not Null)
 
This one does not work:
SELECT "HPD:Help-Desk"."Incident-Number", "HPD:Help-Desk"."Status
History-New-TIME"
FROM "HPD:Help-Desk" "HPD:Help-Desk"
WHERE ("HPD:Help-Desk"."Incident-Number" Is Not Null)
 
**notice the only difference is the addition of Status History New TIME
to the query.

 
I believe this to be an issue with the ARODBC drivers, I even had him
reinstall the user.exe to make sure his driver wasn't corrupted, etc.
I hope someone else has seen this as I am perplexed.
 
Has anyone else had issues with 7.1  and Status.History?
 
Kind Regards,
 
Jase
 
 
ARS 7.1 Patch 002
Win2K5
__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___ 

__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___ 

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to