The main limitation is that you can perform joins in the query using the OBDC driver. If you need to join tables together you need to build them in Remedy first and then use in your report.
The other restriction/feature is that the driver uses the Remedy data security model - so if you can't see something using Remedy you can see it in a report. Stuart Schon Service Desk Systems - Manager Fujitsu Australia Limited Please consider the environment before printing this email -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Tauf Chowdhury Sent: Thursday, 2 May 2013 6:37 AM To: [email protected] Subject: Re: AR System ODBC driver Thanks Fred. I'll check it out. Sent from my iPhone On May 1, 2013, at 4:36 PM, "Grooms, Frederick W" <[email protected]> wrote: > The Integration Guide document (Page 212) lists some issues and > considerations > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Tauf Chowdhury > Sent: Wednesday, May 01, 2013 2:25 PM > To: [email protected] > Subject: AR System ODBC driver > > ** > Version: 7.6.04 > > All, > Does anyone know or have a document about what capabilities are available for the AR System ODBC driver? I have a user who is trying to use Crystal Reports by way of the driver and some features aren't working. > > > -- > Tauf Chowdhury > > ______________________________________________________________________ > _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
