Access Violation @ odbc_fetch_row - but why?

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Sonnich
    #1

    Access Violation @ odbc_fetch_row - but why?

    Hi!

    I get this error: PHP has encountered an Access Violation at 04C3451C

    It occurs at the while line, as I get a and b, but not c. I run this
    a number of times, but the 3 first times it works, at the fourth, which
    returns 2 rows, results in this error at that point.
    Why?

    echo "#a ";
    if(odbc_num_row s($result)>1)
    {
    echo "#b ";
    while(odbc_fetc h_row($result))
    {
    echo "#c ";
    $itemtosearch1[]=odbc_result($r esult,1);
    $itemtosearch2[]=odbc_result($r esult,2);
    }
    }

    Tags: None
    • Sonnich
      #2
      Re: Access Violation @ odbc_fetch_row - but why?


      Sonnich wrote:
      Hi!
      >
      I get this error: PHP has encountered an Access Violation at 04C3451C
      >
      It occurs at the while line, as I get a and b, but not c. I run this
      a number of times, but the 3 first times it works, at the fourth, which
      returns 2 rows, results in this error at that point.
      Why?
      By a closer look the 3 first runs DO NOT return any data.
      The result at the point is still 2 rows.
      >
      echo "#a ";
      if(odbc_num_row s($result)>1)
      {
      echo "#b ";
      while(odbc_fetc h_row($result))
      {
      echo "#c ";
      $itemtosearch1[]=odbc_result($r esult,1);
      $itemtosearch2[]=odbc_result($r esult,2);
      }
      }

        Comment

        • Sonnich
          #3
          Re: Access Violation @ odbc_fetch_row - but why?


          Sonnich wrote:
          Hi!
          >
          I get this error: PHP has encountered an Access Violation at 04C3451C
          >
          It occurs at the while line, as I get a and b, but not c. I run this
          a number of times, but the 3 first times it works, at the fourth, which
          returns 2 rows, results in this error at that point.
          Why?
          By a closer look the 3 first runs DO NOT return any data.
          The result at the point is still 2 rows.
          >
          echo "#a ";
          if(odbc_num_row s($result)>1)
          {
          echo "#b ";
          while(odbc_fetc h_row($result))
          {
          echo "#c ";
          $itemtosearch1[]=odbc_result($r esult,1);
          $itemtosearch2[]=odbc_result($r esult,2);
          }
          }

            Comment

            • Sonnich
              #4
              Re: Access Violation @ odbc_fetch_row - but why?


              Sonnich wrote:
              Hi!
              >
              I get this error: PHP has encountered an Access Violation at 04C3451C
              >
              It occurs at the while line, as I get a and b, but not c. I run this
              a number of times, but the 3 first times it works, at the fourth, which
              returns 2 rows, results in this error at that point.
              Why?
              By a closer look the 3 first runs DO NOT return any data.
              The result at the point is still 2 rows.
              >
              echo "#a ";
              if(odbc_num_row s($result)>1)
              {
              echo "#b ";
              while(odbc_fetc h_row($result))
              {
              echo "#c ";
              $itemtosearch1[]=odbc_result($r esult,1);
              $itemtosearch2[]=odbc_result($r esult,2);
              }
              }

                Comment

                • Chung Leong
                  #5
                  Re: Access Violation @ odbc_fetch_row - but why?

                  Sonnich wrote:
                  Hi!
                  >
                  I get this error: PHP has encountered an Access Violation at 04C3451C
                  >
                  It occurs at the while line, as I get a and b, but not c. I run this
                  a number of times, but the 3 first times it works, at the fourth, which
                  returns 2 rows, results in this error at that point.
                  Why?
                  >
                  echo "#a ";
                  if(odbc_num_row s($result)>1)
                  {
                  echo "#b ";
                  while(odbc_fetc h_row($result))
                  {
                  echo "#c ";
                  $itemtosearch1[]=odbc_result($r esult,1);
                  $itemtosearch2[]=odbc_result($r esult,2);
                  }
                  }
                  >From the memory address, it doesn't look like the it's crashing within
                  the PHP executable. You might be using a broken ODBC driver.

                    Comment

                    • Chung Leong
                      #6
                      Re: Access Violation @ odbc_fetch_row - but why?


                      Sonnich wrote:
                      Hi!
                      >
                      I get this error: PHP has encountered an Access Violation at 04C3451C
                      >
                      It occurs at the while line, as I get a and b, but not c. I run this
                      a number of times, but the 3 first times it works, at the fourth, which
                      returns 2 rows, results in this error at that point.
                      Why?
                      >
                      echo "#a ";
                      if(odbc_num_row s($result)>1)
                      {
                      echo "#b ";
                      while(odbc_fetc h_row($result))
                      {
                      echo "#c ";
                      $itemtosearch1[]=odbc_result($r esult,1);
                      $itemtosearch2[]=odbc_result($r esult,2);
                      }
                      }
                      Message was screwed up by a stray bracket...
                      >From the memory address, it doesn't look like the crash occurs within
                      PHP. The PHP executable starts at the address 0x04000000. It is not
                      large enough to reach 0x04C3451C. phpts#.dll normally starts at
                      0x10000000.

                      It could be that you're using a broken ODBC driver. Look at the crash
                      log, it'll tell you in which DLL the crash actually occurred.

                        Comment

                        Previous template Next
                        Working...