Web студия "GrandView"

add a note User Contributed Notes
odbc_result

baoshenyi at hotmail dot com
17-Mar-2005 10:51


I use one store procedure to retrieve value of identifier, other, name, section,data and datecreated coulmns to variable from SQL server table 



using $odbc_result = odbc_exec($connect,$query); function.



After that, I using following code,

for($f=1;$f<=odbc_num_fields($odbc_result);$f++) {echo "<td style=\"font-weight:bold\">$f ".odbc_field_name($odbc_result,$f)."</td>";}

echo "</tr></table>";

odbc_fetch_row($odbc_result);

echo odbc_result($odbc_result,1)."<br>";

echo odbc_result($odbc_result,2)."<br>";

echo odbc_result($odbc_result,3)."<br>";

echo odbc_result($odbc_result,4)."<br>";

echo odbc_result($odbc_result,5)."<br>";

echo odbc_result($odbc_result,6)."<br>";



The result is as following,

1 identifier 2 other 3 name 4 section 5 data 6 datecreated 

id1

other2

name3

section4

Warning: odbc_result() [function.odbc-result]: SQL error: [Microsoft][ODBC SQL Server Driver]Invalid Descriptor Index, SQL state S1002 in SQLGetData in d:\lawdepot_test\contracts\common\LicensingSQL.php on line 630

2005-03-16 18:12:00



I can not get "data"(Text column) back. Firstly, I think "data" column is too long for odbc_result($odbc_result,5) function, but after I check my old colde, I found I can get the "data" back using same function odbc_result().



I would like to hear any suggestions from you. Depressed on this question.



Michael

vlad dot posea at mymail dot ro
02-May-2003 04:22


i use odbc and mysql and i noticed after losing a lot of time that if you write something like this:

echo odbc_result($result,1); 

....

echo odbc_result($result,1);

the second echo will fail. so it's more useful to save the result of odbc_result in a variable and use it later

like that: $var=odbc_result($result,1);

i hope this will be useful!

spooky
14-Mar-2003 09:27


It took me a while to find out why there was a problem with retrieving data with odbc_result statement.



Warning: SQL error: [Microsoft][ODBC SQL Server Driver]

SQL state S1002 in SQLGetData



State S1002 means that invalid column index has been used.

I checked it hundred times - column index was OK.



Finally i ordered calls of odbc_result statement according to order of fields in the table. It helped.



Best regards

AKA MBG
28-Feb-2003 02:29


About memo fields accessing through ODBC. 

I got error:



SQL error: [Microsoft][ODBC Visual FoxPro Driver]Invalid cursor position, SQL state S1109 in SQLGetData SQL error...



In fact there is no necessity to change Memo to Text type of field in database. Example of source code:



class ds_fconstr extends db_base_table

{

  var $db_fields  = array('name' => "",

                         'password' => "");



  $query = "SELECT * FROM ds_fconstr";

  $odbc  = odbc_connect (DB_DSN, "", "")

  $req = odbc_exec ($odbc, $query)



  // create this class

  $temp = new ds_fconstr();



  // error inside of this function (of parent class)

  // when try call "odbc_result" for "memo" field

  $temp->setFieldsValue ($req);



   // all OK here

  foreach ($temp->db_fields as $name => $value)

  {

    $temp->db_fields[$name] = odbc_result($req,$name);

  }

}



// where base class is following

Class db_base_table

{

  var $db_fields = array();

        

  // set value of fields from fetched row

  // ----------------------------

  function setFieldsValue($req)

  {

      foreach ($this->db_fields as $name => $value)

      {

          // error is HERE (only for "memo" fields, others are ok),

        // because (possible) PHP do not transfer

        // correctly result of odbc_exec with "memo"

        $this->db_fields[$name] = odbc_result($req,$name);

      }

    }

};



So, when i call directly "odbc_result" in the same function where i have called "odbc_exec" then all is right (see line "// all OK here").

22-Jan-2003 06:43


From http://www.php.net/manual/en/function.odbc-longreadlen.php but relevant here, also. 



An alternative is to adjust your php.ini file and set:

odbc.defaultlrl=65536

Or something else sufficiently large.

lrl = long read length



to get around the limit on returned chars.

fate at doityourself dot com
20-Jan-2003 09:14


if you want to quickly change a website from odbc- to mysql-data-access, you could use a simple function like this one:

function myresult ($cur,$nr) { 

   return mysql_result($cur,0,mysql_field_name($cur,$nr-1)); 

}

and just do a global replace from "odbc_result" to "myresult".



beware, you should only use this if you don't care too much about performance, as this will start a query for every field you request - the better way is of course using mysql_fetch_row!

murat at nospam dot robcol dot k12 dot tr
15-Jul-2002 02:44


When trying to get a date/time field from an Access database, odbc_result returns the date as text (e.g. 1998-07-11 21:12:23). You may use strtotime function to convert this into a format which can be used with PHP.



e.g.

echo "The date is "

 .date("r",strtotime(odbc_result($myquery,"mydate")));

huevo dot SP at M dot earthling dot net
31-Jul-2001 03:46


With an Access 2K database, odbc_result will only work the first time it is called on a memo field (odbc_field_type returns 'LONGCHAR').



$good = odbc_result($result,'Description');

# $good holds the field value

$fail = odbc_result($result,'Description');

# $fail holds false



This tripped me up when I did something like this:



for ($i=1; $i<=odbc_num_fields($result); $i++) {

  if(odbc_result($result,$i)){

    ... more code ...

    echo odbc_result($result,$i);

    ... snip ...

  }

}



For any field type except memo, this code works perfectly.  But on memo fields, odbc_result returns false on the second call and nothing is echoed.



Be careful, use a temporary variable instead of multiple calls to odbc_result.  (It's good programming practice anyway)



for (...) {

  $temp = odbc_result($result,$i);

  if($temp){

    ...

    echo $temp;

    ...

  }

}

user at frosch dot org
30-May-2001 08:55


Hopefully useful note on accessing TEXT fields on Windows, using PHP's ODBC support to access Sybase*. With the following code:



"SELECT status AS projstatus,oid AS projident,LOWER(title) AS projtitel,startsOn AS projanfang,terminatesOn AS projende,description AS projinfo FROM Project ORDER BY projtitel ASC"



I was getting a strange error:



  Warning: SQL error: [INTERSOLV][ODBC SQL Server driver][SQL Server]Invalid column name 'projanfang'. , SQL state S0022 in SQLGetData in [**scriptname and path removed**] on line 126



even though I was clearly selecting a field as 'projanfang'. The reason I worked out eventually is that Sybase/ODBC attempts to do a conversion on the TEXT field 'description', which fails since the limit for CONVERT is 255 characters, and TEXT is a field type with a  2 GB limit. I am not sure why it doesn't work implicitly, but it does explicitly. The following code will work without errors:



  "SELECT status AS projstatus,oid AS projident,LOWER(title) AS projtitel,startsOn AS projanfang,terminatesOn AS projende,CONVERT(CHAR(255),description) AS projinfo FROM Project ORDER BY projtitel ASC"



What you do if you have a need for more than 255 characters of your text field, I do not know :(. I have also tried longreadlen, but I couldn't work out how it could be used.



* System details: Windows NT 4.0 SP6a, IIS 4.0, Sybase 11.5 Adaptive Enteprise, PHP 4.0.5.

09-Mar-2001 12:29


Estou adicionando esta mensagem porque demorei a conseguir executar um determinado procedimento.

Se voc