Current recordset does not support updating this may be

It worked after we compiled with --ibm-db2= option, but it was unbelievable slow.

No, just testing some options, we found out that it went from very slow (getting 100 records lasts 1 till 10 seconds) to fast access (almost same speed as with using JDBC from Servlets) to 0.2 till 0.3 seconds.

The solution I fund working is to perform the following changes to Windows Control Panel WINNT 4 Workstation, PHP4 odbc_connect() kept giving me weird errors when trying to connect to a MSaccess DSN(Microsoft Jet engine couldn't open the database 'Unknow'.

current recordset does not support updating this may be-23current recordset does not support updating this may be-56current recordset does not support updating this may be-90

My workaround was to design my script exit entirely after a the database update had completed.

O quarto parâmetro, que é opcional, define o tipo de cursor para ser utilizado nesta conexão.

Este parâmetro normalmente não é necessário, mas pode ser útil para contornar problemas com alguns drivers ODBC.

When you pull up the usual menu for the odbc / dsn system, it is for the 64 bit odbc manager, and 32 bit applications (vb 6.0, PHP 5) will not work using these dsn's.

This is where the 32 bit odbc manager is: C:\Windows\Sys WOW64\odbcad32here's a quick note about using php and db2 that cost me a couple of hours and several recompiles trying to figure out why it didn't the below line in any script putenv("DB2INSTANCE=db2inst1"); Or, set that in your webserver environment somehow. I'm using Apache 2.0.39 on Windows XP and PHP 4.2.2.

Leave a Reply