|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2003-09-11 22:08 UTC] michaelc at mikeit dot com dot au
[2003-09-11 22:23 UTC] sniper@php.net
[2003-09-11 23:30 UTC] kalowsky@php.net
[2003-09-16 00:39 UTC] michaelc at mikeit dot com dot au
[2003-09-16 08:39 UTC] kalowsky@php.net
[2003-09-22 06:46 UTC] sniper@php.net
[2005-02-10 00:05 UTC] moreinfo at potentialtech dot com
|
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Fri Oct 24 04:00:01 2025 UTC |
Description: ------------ Trying to write a php gtk frontend to a MYOB (manage your own business) database. They provide a suitably crippled ODBC driver, which via Perl, I can determine that it supports only SQLFetch, rather than PHP's default of SQLExtendedFetch. I know how to recompile on linux to change PHP's behavious, but how would I do this on Win32 ? Is there an .ini flag, or SQL command option I can set to work around this ? Is there any chance of getting PHP to implement a flag as to what SQL fetch command it uses for ODBC ? Not that that the exec function actually works, and returns data, and the program works correctly up until I terminate where I get the error message on exit. Reproduce code: --------------- <?php if (!class_exists('gtk')) { if (strtoupper(substr(PHP_OS, 0, 3)) == 'WIN') dl('php_gtk.dll'); else dl('php_gtk.so'); } function delete_event() { return false; } $connectionstring = odbc_connect("MYOB","michaelc","") or die(odbc_error()); $query = "SELECT * FROM Cards"; $queryexe = odbc_do($connectionstring, $query); odbc_close($connectionstring); $window = &new GtkWindow(); $window->connect_object('destroy', array('gtk', 'main_quit')); $window->connect('delete-event', 'delete_event'); $window->set_title('PHP Rules!'); $window->set_name('MainWindow'); $window->set_usize(150, 200); $window->show_all(); /* Run the main loop. */ Gtk::main(); ?> Actual result: -------------- The instruction at "0x01c7e090" referenced memory at "0x01ca5170". The memory could not be "read". On exit of program, program runs successful until this point.