accessing Sybase Remedy DB from UNIX...

2007-06-11 Thread a.cook
Hi there, I was wondering... I have several PHP scripts that I am running from Windows to query our company's Remedy DB (Sybase). I am using the default Remedy ODBC that gets installed when Remedy is installed in Windows (see http://cookandy.com/odbc3.JPG). I am trying to get the scripts

Re: converting excel ARS query to php

2007-06-05 Thread a.cook
if that works. If it does, then starting adding the columns you need. My guess is one of the columns is a CLOB or BLOB and PHP does like it. On 6/4/07, a.cook [EMAIL PROTECTED] wrote: Hello, I have an Excel Macro that is querying an ARS db. Everything works fine. I'm trying to port the query over

Re: converting excel ARS query to php

2007-06-05 Thread a.cook
that this is a Sybase DB. Should that make a difference? The whole ODBC/Sybase thing is new to me. I'm used to working with mySQL. Frank Caruso-2 wrote: I think the name of the view is just Incident_Management. On 6/5/07, a.cook [EMAIL PROTECTED] wrote: Thanks for the reply. I replaced the query

Re: converting excel ARS query to php

2007-06-05 Thread a.cook
...so the space and second iteration are useless in this case. If you pull up Sybase...is that the name of the view that your looking at? -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of a.cook Sent: Tuesday, June 05

Re: converting excel ARS query to php

2007-06-05 Thread a.cook
...which means your form name is whatever it shows in the Admin tool for that form...Incident_Management is the DB View nametry that and let us know -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of a.cook Sent: Tuesday

converting excel ARS query to php

2007-06-04 Thread a.cook
Hello, I have an Excel Macro that is querying an ARS db. Everything works fine. I'm trying to port the query over to PHP on the same machine but I am getting an error. Here is the query from Excel: SELECT Incident_Management.Incident_Id, Incident_Management.Account_Affected__,