imho, msaccess is not fit for driving an entire content management system. MsAccess is an personal-or-single-user dbms, too often abused for applications where a real RDBMS should be used.
On the otehr hand, you could try to write a driver in ezpublish for msaccess.
Thanx for the input.. I completely feel the same way about MS-Access. Whil our real objective is to use SQL Server 7.0 / 2000 as the RDBMS, we wanted to try out ezPublish's capability and scalability on working with MS products. Hence we are testing the same using MS-Access. The Ultimate objective is to try and use MS-SQL Server 7.0 / 2000 as the RDBMS, Can U throw some insight as to how i can achieve the same..?? either on MS-Access or on MS-SQL Server..??
If I have understood the eZ kernel correct, one sollution is to write a eZodbcDB class as an extension. You have to write it the same way as eZMySQLDB is written.
You probably also need to do some changes to eZDb to be able to support it (this I'm not sure, it depends on how good the code is).
I'm not sure thow if the odbc support in PHP is sufficient to run eZ over odbc.
I'm solving a similar problem now, but I'm going to use the MySQL database for all eZmodules, but I'll make modules to access data from i.e MS SQL.
Frode Marton Meling
You must be logged in to post messages in this topic!
