|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2001-05-31 07:56 UTC] phanto@php.net
[2001-05-31 08:15 UTC] peter at helpnet dot com dot au
[2001-06-07 06:15 UTC] peter at helpnet dot com dot au
[2001-10-04 14:36 UTC] phanto@php.net
|
|||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Fri Oct 24 01:00:02 2025 UTC |
PHP 4.0.5 COM The following code makes Apache blow up with an access violation: if($w = new com("word.application")) { if($w->Visible = 1) { print("<br>Word should be visible." ); I tried it with PHP 4.0.5 and Apache 1.13.19 then updated Apache to 1.13.20 with the same result. Reverting to PHP 4.0.4pl1 stopped Apache blowing up but Word is not becoming visible, which indicates the Visible property is not doing anything. Apache runs PHP as isapi and here is the relevant part of the .conf: LoadModule php4_module "c:/Program files/php/sapi/php4apache.dll" AddType application/x-httpd-php .html AddType application/x-httpd-php .php Because Word is not becoming visible, some Word error messages are not displayed and the results of unanswered errors, explaining some of the weird problems people report with COM, such as applications locking up on second and subsequent entry. If I manually make Word visible, by starting the application, the document handled by COM does not become visible and the errors remain locked up. I am using NT 4.0 with SP6 and MS Office is 97 with SR-2. 97 is the latest release I can install without being stuck with Internet Exploder. If you have a binary to test, I can install it any time. I will use COM on 4.0.4pl1 for a couple more days then go back to 4.0.5 so I can experiment with the lastest functions for images.