Over 60% of websites use Apache. Many people using MySQL and PHP also run
Apache for the complete open source solution. This is cheap to set up, and
easy to get support for (there's even a mailing list called AMP -
Apache/MySQL/PHP). And, IIRC, those on NT 4.0 Workstation don't *have* IIS.
It's easy to configure and maintain, is constantly being upgraded and
bug-fixed, and has tons of support and reference online.
Just my 0.02 euros, obviously.
Cheers
Jon
-----Original Message-----
From: Dan Malcolm [mailto:[EMAIL PROTECTED]]
Sent: 02 February 2001 11:49
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [PHP] For My Information
I see in the posts, that a lot of people are using Apache on NT instead of
the built in IIS. Is there a reason? I have PHP up and running with dBase
tables converted to MySQL and ODBC connected to Access 2000, on an NT 4 box
with IIS 4 and it runs very well. Performance is great. My only problem is
automating the conversion to update tables in MySQL. I would like like to
convert the Access 2000 tables also but the converters either don't seem to
work with Access 2k, or not much at all, or are not such that a timed batch
file can be generated using them. I just looked at what I've written and
it's a little jumbled. Mega-Sigh. Let me summarize.
1.. Why Apache on NT 4.0?
2.. Is there a good way to automatically convert Access 2000 to MySQL to
keep MySQL data up to date? The data needs to be updated several times a
week. No I can't just switch everything over and not have to convert again.
3.. A way to do #2 for dBase would be good too, but less critical because
the data only gets updated every couple months.
Thanks in advance.
Dan Malcolm
[EMAIL PROTECTED]
[EMAIL PROTECTED]
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
