>mweb,
> To make sure I understand you correctly, you want to create
>and
>test your PHP/MySQL database on your Linux/Apache box, then upload it
>to
>your ISP server that is running PHP/Access? I'm sorry but that's not
>going
>to work. You can't transparently switch a PHP application from MySQL
>to
>Access.
Yes, you did understand me correctly.
What I understand ( and could certainly be wrong) is that there are in
PHP layers of abstraction/wrappers/APIs or whatever you call them,
that allow you to do just that, i.e. to write code that is obviously
not as efficient as one written specifically for one single database,
but does work on more of them.
As a matter of fact, after posting the first message, I bought the
book PHP developers cookbook which has section 16.0 named more or less
How to create a DB independent API with PHP, and that says "at the
beginning of the script is included a file containing all the wrapper
function....."
That's exactly what I was hoping to do. THe site has ~4000
accesses/month, and just some hundred records in the DB, so performance
is not really an issue here, is it?
Any further thoughts/comments/suggestions/snippets of code?
Did really nobody ever face this problem before?
mweb
--
Whatever you do will be insignificant, but it is very important that
you do it. -- Gandhi
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
