Sorry yes your right Fred, I meant that you CAN'T use dynamic joins (i.e. in the SQL) when using the OBDC driver. And as you pointed out you CAN'T see anything your userid is not supposed to see in the report.
Using sub-reports is a real solution but it can be really really slow if a significant number of parent records are being processed. Use of the ODBC driver has significant benefits as it decodes many of the DB field values into nice things like dates and readable Strings for things such as Status. You can also test dates in your query without having to decode them to epoch values. Stuart Schon Service Desk Systems - Manager Fujitsu Australia Limited -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Grooms, Frederick W Sent: Thursday, 2 May 2013 11:42 PM To: [email protected] Subject: Re: AR System ODBC driver I think Stuart had a typo ... Since the ODBC uses the Remedy application server, if you can't see something in Remedy you can't see it using the ODBC driver. One way around the join limitation is to use sub-reports in Crystal. You can then have multiple form(s) data in the report Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Schon, Stuart Sent: Wednesday, May 01, 2013 6:13 PM To: [email protected] Subject: Re: AR System ODBC driver 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't 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"
