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
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
