**
Hi,

We have a 3rd party trying to integrate to our AR System platform and ideally we'd like them to 'read' via the AR System ODBC driver then they can make use of the date translation abilities etc...

However when they connect using an application called SCRIBE and select the AR System ODBC datasource as an ODBC data source it fails to return any forms or rows, if they use the raw Oracle ODBC connector they can see the raw tables etc... quite happily... are the known limitations using the ODBC connector with certain apps?

Has anyone successfully used SCRIBE and the ARSystem ODBC datasource?

Config info:

AR System 6.0.3 patch 11
App Server: Solaris
DB Server: Oracle 9.2.0 patch 4
DB Platform: Solaris
Application: SCRIBE
SCRIBE Server: Windows Server 2003

Crystal runs fine on the same server using AR System ODBC as does our Crystal Reports Distribution program, we've used Excel successfully on said server, but SCRIBE just fails to be able to use the ODBC connection...

All constructive suggestions appreciated.

Stephen
20060125This posting was submitted with HTML in it

**

Stephen,

While configuring the ODBC driver did they specify a Remedy user that has the rights to see all the tables you need to see.. Bear in mind that the Remedy ODBC driver respects the permission set you have defined in Remedy on the forms...

Joe D'Souza
Remedy Developer / Consultant,
Shyle Networks,
New Jersey.

Stephen Earl wrote:

**
Hi,

We have a 3rd party trying to integrate to our AR System platform and ideally we'd like them to 'read' via the AR System ODBC driver then they can make use of the date translation abilities etc...

However when they connect using an application called SCRIBE and select the AR System ODBC datasource as an ODBC data source it fails to return any forms or rows, if they use the raw Oracle ODBC connector they can see the raw tables etc... quite happily... are the known limitations using the ODBC connector with certain apps?

Has anyone successfully used SCRIBE and the ARSystem ODBC datasource?

Config info:

AR System 6.0.3 patch 11
App Server: Solaris
DB Server: Oracle 9.2.0 patch 4
DB Platform: Solaris
Application: SCRIBE
SCRIBE Server: Windows Server 2003

Crystal runs fine on the same server using AR System ODBC as does our Crystal Reports Distribution program, we've used Excel successfully on said server, but SCRIBE just fails to be able to use the ODBC connection...

All constructive suggestions appreciated.

Stephen



Yahoo! Mail
Use Photomail to share photos without annoying attachments. 20060125This posting was submitted with HTML in it

**
Joe,

Yes when we were testing we tried a restricted user, and also used my login which is administrator, thus should have access to all forms/tables needed.

Stephen


On 14/03/06, Joe DeSouza wrote:

**

Stephen,

While configuring the ODBC driver did they specify a Remedy user that has the rights to see all the tables you need to see.. Bear in mind that the Remedy ODBC driver respects the permission set you have defined in Remedy on the forms...

Joe D'Souza
Remedy Developer / Consultant,
Shyle Networks,
New Jersey.

Stephen Earl wrote:

**

Hi,

We have a 3rd party trying to integrate to our AR System platform and ideally we'd like them to 'read' via the AR System ODBC driver then they can make use of the date translation abilities etc...

However when they connect using an application called SCRIBE and select the AR System ODBC datasource as an ODBC data source it fails to return any forms or rows, if they use the raw Oracle ODBC connector they can see the raw tables etc... quite happily... are the known limitations using the ODBC connector with certain apps?

Has anyone successfully used SCRIBE and the ARSystem ODBC datasource?

Config info:

AR System 6.0.3 patch 11
App Server: Solaris
DB Server: Oracle 9.2.0 patch 4
DB Platform: Solaris
Application: SCRIBE
SCRIBE Server: Windows Server 2003

Crystal runs fine on the same server using AR System ODBC as does our Crystal Reports Distribution program, we've used Excel successfully on said server, but SCRIBE just fails to be able to use the ODBC connection...

All constructive suggestions appreciated.

Stephen




Yahoo! Mail
Use Photomail to share photos without annoying attachments. 20060125This posting was submitted with HTML in it




20060125This posting was submitted with HTML in it

**
Any errors when you try to log on to the AR Server using the AR ODBC driver?

Joe D'Souza
Remedy Developer / Consultant,
Shyle Networks,
New Jersey.

Stephen Earl wrote:

**
Joe,

Yes when we were testing we tried a restricted user, and also used my login which is administrator, thus should have access to all forms/tables needed.

Stephen


On 14/03/06, Joe DeSouza wrote:

**

Stephen,

While configuring the ODBC driver did they specify a Remedy user that has the rights to see all the tables you need to see.. Bear in mind that the Remedy ODBC driver respects the permission set you have defined in Remedy on the forms...

Joe D'Souza
Remedy Developer / Consultant,
Shyle Networks,
New Jersey.

Stephen Earl wrote:

**

Hi,

We have a 3rd party trying to integrate to our AR System platform and ideally we'd like them to 'read' via the AR System ODBC driver then they can make use of the date translation abilities etc...

However when they connect using an application called SCRIBE and select the AR System ODBC datasource as an ODBC data source it fails to return any forms or rows, if they use the raw Oracle ODBC connector they can see the raw tables etc... quite happily... are the known limitations using the ODBC connector with certain apps?

Has anyone successfully used SCRIBE and the ARSystem ODBC datasource?

Config info:

AR System 6.0.3 patch 11
App Server: Solaris
DB Server: Oracle 9.2.0 patch 4
DB Platform: Solaris
Application: SCRIBE
SCRIBE Server: Windows Server 2003

Crystal runs fine on the same server using AR System ODBC as does our Crystal Reports Distribution program, we've used Excel successfully on said server, but SCRIBE just fails to be able to use the ODBC connection...

All constructive suggestions appreciated.

Stephen




Yahoo! Mail
Use Photomail to share photos without annoying attachments. 20060125This posting was submitted with HTML in it

20060125This posting was submitted with HTML in it





Yahoo! Mail
Use Photomail to share photos without annoying attachments. 20060125This posting was submitted with HTML in it

**
Stephen,
Is the SCRIBE application connecting via a custom-defined 'System DSN' that uses the AR System ODBC driver (recommended), or is it attempting a connection via the default 'User DSN' entry for the driver?

--Thomas


----- Original Message -----
From: Stephen Earl
Newsgroups: gmane.comp.crm.arsystem.general
Sent: Tuesday, March 14, 2006 11:25
Subject: Re: AR System ODBC Driver and SCRIBE

**
Joe,

Yes when we were testing we tried a restricted user, and also used my login which is administrator, thus should have access to all forms/tables needed.

Stephen


On 14/03/06, Joe DeSouza wrote:

**

Stephen,

While configuring the ODBC driver did they specify a Remedy user that has the rights to see all the tables you need to see.. Bear in mind that the Remedy ODBC driver respects the permission set you have defined in Remedy on the forms...

Joe D'Souza
Remedy Developer / Consultant,
Shyle Networks,
New Jersey.

Stephen Earl wrote:

**

Hi,

We have a 3rd party trying to integrate to our AR System platform and ideally we'd like them to 'read' via the AR System ODBC driver then they can make use of the date translation abilities etc...

However when they connect using an application called SCRIBE and select the AR System ODBC datasource as an ODBC data source it fails to return any forms or rows, if they use the raw Oracle ODBC connector they can see the raw tables etc... quite happily... are the known limitations using the ODBC connector with certain apps?

Has anyone successfully used SCRIBE and the ARSystem ODBC datasource?

Config info:

AR System 6.0.3 patch 11
App Server: Solaris
DB Server: Oracle 9.2.0 patch 4
DB Platform: Solaris
Application: SCRIBE
SCRIBE Server: Windows Server 2003

Crystal runs fine on the same server using AR System ODBC as does our Crystal Reports Distribution program, we've used Excel successfully on said server, but SCRIBE just fails to be able to use the ODBC connection...

All constructive suggestions appreciated.

Stephen




Yahoo! Mail
Use Photomail to share photos without annoying attachments. 20060125This posting was submitted with HTML in it






20060125This posting was submitted with HTML in it

20060125This posting was submitted with HTML in it

**
I do not think its flaky too, you might need to do certain things that may not be very clearly documented to get it to work, but once you get it to work it is pretty consistent.

The problem with SCRIBE seems to be more of how SCRIBE is handling the driver.. They could try running a network snoop to see if SCRIBE is sending any packets at all forward to the server while attempting to log on to the Remedy server via the ODBC, and if not it would mean there is something wrong with SCRIBE itself... not the ODBC driver as he says it works well with other apps...

Joe

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



Relax. Yahoo! Mail virus scanning helps detect nasty viruses! 20060125This posting was submitted with HTML in it

**
Thomas,

I've tried both, system and user with the same results, after discussions with Joe I'm pretty convinced it's a SCRIBE problem as we now have got as far as an error from scribe of:

Data source label SOURCE not found

I'm going to see if it even tries to connect or if it's an internal error...




On 14/03/06, Thomas Bean wrote:

**
Stephen,
Is the SCRIBE application connecting via a custom-defined 'System DSN' that uses the AR System ODBC driver (recommended), or is it attempting a connection via the default 'User DSN' entry for the driver?


--Thomas



----- Original Message -----
From: Stephen Earl
Newsgroups: gmane.comp.crm.arsystem.general
Sent: Tuesday, March 14, 2006 11:25
Subject: Re: AR System ODBC Driver and SCRIBE


**
Joe,

Yes when we were testing we tried a restricted user, and also used my login which is administrator, thus should have access to all forms/tables needed.

Stephen


On 14/03/06, Joe DeSouza wrote:

**

Stephen,

While configuring the ODBC driver did they specify a Remedy user that has the rights to see all the tables you need to see.. Bear in mind that the Remedy ODBC driver respects the permission set you have defined in Remedy on the forms...

Joe D'Souza
Remedy Developer / Consultant,
Shyle Networks,
New Jersey.

Stephen Earl wrote:

**

Hi,

We have a 3rd party trying to integrate to our AR System platform and ideally we'd like them to 'read' via the AR System ODBC driver then they can make use of the date translation abilities etc...

However when they connect using an application called SCRIBE and select the AR System ODBC datasource as an ODBC data source it fails to return any forms or rows, if they use the raw Oracle ODBC connector they can see the raw tables etc... quite happily... are the known limitations using the ODBC connector with certain apps?

Has anyone successfully used SCRIBE and the ARSystem ODBC datasource?

Config info:

AR System 6.0.3 patch 11
App Server: Solaris
DB Server: Oracle 9.2.0 patch 4
DB Platform: Solaris
Application: SCRIBE
SCRIBE Server: Windows Server 2003

Crystal runs fine on the same server using AR System ODBC as does our Crystal Reports Distribution program, we've used Excel successfully on said server, but SCRIBE just fails to be able to use the ODBC connection...

All constructive suggestions appreciated.

Stephen




Yahoo! Mail
Use Photomail to share photos without annoying attachments. 20060125This posting was submitted with HTML in it








20060125This posting was submitted with HTML in it

20060125This posting was submitted with HTML in it


20060125This posting was submitted with HTML in it

Do keep in mind that Remedy's ARODBC driver is flaky at best.
Supported ODBC call types are extremely limited.

Axton Grams

On 3/15/06, Stephen Earl wrote:
> **
> Thomas,
>
> I've tried both, system and user with the same results, after discussions
> with Joe I'm pretty convinced it's a SCRIBE problem as we now have got as
> far as an error from scribe of:
>
> Data source label SOURCE not found
>
> I'm going to see if it even tries to connect or if it's an internal error...
>
>
>
>
> On 14/03/06, Thomas Bean wrote:
> > **
> > Stephen,
> > Is the SCRIBE application connecting via a custom-defined 'System DSN'
> that uses the AR System ODBC driver (recommended), or is it attempting a
> connection via the default 'User DSN' entry for the driver?
> >
> > --Thomas
> >
> >
> > ----- Original Message -----
> > From: Stephen Earl
> > Newsgroups: gmane.comp.crm.arsystem.general
> > Sent: Tuesday, March 14, 2006 11:25
> > Subject: Re: AR System ODBC Driver and SCRIBE
> >
> >
> > **
> > Joe,
> >
> > Yes when we were testing we tried a restricted user, and also used my
> login which is administrator, thus should have access to all forms/tables
> needed.
> >
> > Stephen
> >
> >
> > On 14/03/06, Joe DeSouza wrote:
> > > **
> > >
> > > Stephen,
> > >
> > > While configuring the ODBC driver did they specify a Remedy user that
> has the rights to see all the tables you need to see.. Bear in mind that the
> Remedy ODBC driver respects the permission set you have defined in Remedy on
> the forms...
> > >
> > > Joe D'Souza
> > > Remedy Developer / Consultant,
> > > Shyle Networks,
> > > New Jersey.
> > >
> > > Stephen Earl wrote:
> > > **
> > >
> > > Hi,
> > >
> > > We have a 3rd party trying to integrate to our AR System platform and
> ideally we'd like them to 'read' via the AR System ODBC driver then they can
> make use of the date translation abilities etc...
> > >
> > > However when they connect using an application called SCRIBE and select
> the AR System ODBC datasource as an ODBC data source it fails to return any
> forms or rows, if they use the raw Oracle ODBC connector they can see the
> raw tables etc... quite happily... are the known limitations using the ODBC
> connector with certain apps?
> > >
> > > Has anyone successfully used SCRIBE and the ARSystem ODBC datasource?
> > >
> > > Config info:
> > >
> > > AR System 6.0.3 patch 11
> > > App Server: Solaris
> > > DB Server: Oracle 9.2.0 patch 4
> > > DB Platform: Solaris
> > > Application: SCRIBE
> > > SCRIBE Server: Windows Server 2003
> > >
> > > Crystal runs fine on the same server using AR System ODBC as does our
> Crystal Reports Distribution program, we've used Excel successfully on said
> server, but SCRIBE just fails to be able to use the ODBC connection...
> > >
> > > All constructive suggestions appreciated.
> > >
> > > Stephen
> > >
> > >
> Yahoo! Mail
> > > Use Photomail to share photos without annoying attachments.
> 20060125This posting was submitted
> with HTML in it
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > 20060125This posting was
> submitted with HTML in it
> > 20060125This posting was
> submitted with HTML in it
>
> 20060125This posting was submitted
> with HTML in it


UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org

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

** If you want to see if the SCRIBE system is logging in to the server you can also turn on the user logs on the AR server and look if there are any entries in there.
If someone connects through the ODBC driver you'd have to see an entry in the user.log

Regards,
Michiel


On 3/15/06, Joe DeSouza wrote:

**
I do not think its flaky too, you might need to do certain things that may not be very clearly documented to get it to work, but once you get it to work it is pretty consistent.

The problem with SCRIBE seems to be more of how SCRIBE is handling the driver.. They could try running a network snoop to see if SCRIBE is sending any packets at all forward to the server while attempting to log on to the Remedy server via the ODBC, and if not it would mean there is something wrong with SCRIBE itself... not the ODBC driver as he says it works well with other apps...

Joe


Carey Matthew Black < black.123@GMAIL.COM > 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




Relax. Yahoo! Mail virus scanning helps detect nasty viruses! 20060125This posting was submitted with HTML in it




20060125This posting was submitted with HTML in it

**
All, thanks for the feedback and input, I'm sorry I haven't responded today, been a little busy.

I'll try all you have suggested and let you know how we get on.


On 15/03/06, Michiel Beijen wrote:

** If you want to see if the SCRIBE system is logging in to the server you can also turn on the user logs on the AR server and look if there are any entries in there.
If someone connects through the ODBC driver you'd have to see an entry in the user.log

Regards,
Michiel



On 3/15/06, Joe DeSouza wrote:

**
I do not think its flaky too, you might need to do certain things that may not be very clearly documented to get it to work, but once you get it to work it is pretty consistent.

The problem with SCRIBE seems to be more of how SCRIBE is handling the driver.. They could try running a network snoop to see if SCRIBE is sending any packets at all forward to the server while attempting to log on to the Remedy server via the ODBC, and if not it would mean there is something wrong with SCRIBE itself... not the ODBC driver as he says it works well with other apps...

Joe


Carey Matthew Black < black.123@GMAIL.COM > 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




Relax. Yahoo! Mail virus scanning helps detect nasty viruses! 20060125This posting was submitted with HTML in it




20060125This posting was submitted with HTML in it


20060125This posting was submitted with HTML in it

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

**
I have managed to fix most of the compatibility issues by 'tricking' the ARS to believe it is connecting to the compatible version of CR by replacing the CR dll files of the older compatible versions and have had no problems with it on doing so..off course Remedy Support would say this method is not supported but I figure if its going to only read the database you got not much to loose by using this trick..

I've had problems once with the way higher versions of CR would handle diary fields and clob fields in general but these went away on replacing the dll's with the older version..

I still think once you get those loose ends chopped it does work nicely...

Joe

Axton wrote:

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



Yahoo! Travel
Find great deals to the top 10 hottest destinations! 20060125This posting was submitted with HTML in it

Call it what you want. The org that writes it won't support it when
used in the way you say. The product the vendor chooses for report
generation does not work when you patch the report generation tool.
The report writing tool chosen by the vendor is very limited in what
it can do and nothing there restricts you from doing what they didn't
account for in their driver.

Give it a name. I chose flaky.

Axton Grams

On 3/15/06, Joe DeSouza wrote:
> **
> I have managed to fix most of the compatibility issues by 'tricking' the ARS
> to believe it is connecting to the compatible version of CR by replacing the
> CR dll files of the older compatible versions and have had no problems with
> it on doing so..off course Remedy Support would say this method is not
> supported but I figure if its going to only read the database you got not
> much to loose by using this trick..
>
> I've had problems once with the way higher versions of CR would handle diary
> fields and clob fields in general but these went away on replacing the dll's
> with the older version..
>
> I still think once you get those loose ends chopped it does work nicely...
>
> Joe
>
>
> Axton wrote:
>
> 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
>
>
>
>
> Yahoo! Travel
> Find great deals to the top 10 hottest destinations!
> 20060125This posting was submitted
> with HTML in it
>
>


UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org

**
Yup I guess so.. I just enjoyed playing around with it to make it work.. One of the version changes when Perigrine took over, even required the ODBC driver name to be Remedy ODBC driver, and the new name AR System ODBC driver caused it to not work! I found that one a bit strange.. I had to make the necessary changes even in the registry to make it work.. was kind of fun when you have a bit of time to play around..

Joe

Axton wrote:

Call it what you want. The org that writes it won't support it when
used in the way you say. The product the vendor chooses for report
generation does not work when you patch the report generation tool.
The report writing tool chosen by the vendor is very limited in what
it can do and nothing there restricts you from doing what they didn't
account for in their driver.

Give it a name. I chose flaky.

Axton Grams

On 3/15/06, Joe DeSouza wrote:
> **
> I have managed to fix most of the compatibility issues by 'tricking' the ARS
> to believe it is connecting to the compatible version of CR by replacing the
> CR dll files of the older compatible versions and have had no problems with
> it on doing so..off course Remedy Support would say this method is not
> supported but I figure if its going to only read the database you got not
> much to loose by using this trick..
>
> I've had problems once with the way higher versions of CR would handle diary
> fields and clob fields in general but these went away on replacing the dll's
> with the older version..
>
> I still think once you get those loose ends chopped it does work nicely...
>
> Joe
>
>
> Axton wrote:
>
> 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
>
>
>
>
> Yahoo! Travel
> Find great deals to the top 10 hottest destinations!
> 20060125This posting was submitted
> with HTML in it
>
>


UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org





Yahoo! Mail
Bring photos to life! New PhotoMail makes sharing a breeze. 20060125This posting was submitted with HTML in it

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