hello worldwide XOOPS users!!!

just to know if any of you ever had a XOOPS over MSSQL database working???

i'm currently trying to hack XOOPS DAO to mount on MSSQL using mssql.dll, still i didn't succeed. bloody blank pages showing! i can't go through the debugging

i'll soon let you know about my experiences
but as i'm not a skilled XOOPS core hacker, i may be passing through something important...

requesting feedbacks!!


jerome [fr]
jetbuch@yahoo.fr

i'm using easyphp 1.8 (Apache 1.3.33, PHP 4.3.10, MySQL 4.1.9) & MSSQL server running on localhost

i modified php.ini to enable mssql dll extension
then restarted php server

copied all tables and contents from MySQL to mssql

using modified mysqldatabase.php to launch mssql functions through mssql dll


mainfile.php follows:

[...]
define('XOOPS_DB_TYPE', 'mysql'); // mssql calls from MySQL old file
define('XOOPS_DB_PREFIX', 'xoops');
define('XOOPS_DB_HOST', 'localhost,1433'); // not sure!
define('XOOPS_DB_USER', 'sa');
define('XOOPS_DB_PASS', '');
define('XOOPS_DB_NAME', 'xump');
define('XOOPS_DB_PCONNECT', 0);
[...]

and i got:

Error [Xoops]: Unable to connect to database in file c:\program files\easyphp1-8\www\xump\class\database\databasefactory.php line 34

modified mysqldatabase.php will soon follows. i'm using a modified mysqldatabase.php to handle mssql calls. The file is from another french xoopser who got the stuff working
a few months ago.

stay tunned

I'll be interested to hear progress on this as support for MS-SQL would be valueable for a lot of business environments.

After some research online, it seems like SQL SERV doesn't basically accept every connection from web apps so easily

found on microsoft MSSQL support website:
_________________________________

Q: Regarding the 1433 question, what if you have clients accessing SQL through the Web and MS Access. How do you give them access if 1433 is closed?

A: Close 1433 on the firewall. I assume the Access clients are coming in via LAN connection, so they bypass the firewall. Is this assumption correct?
__________________________________

of course they just hinted at MS ACCESS in their answer!!!!! :P

so i got to check this port stuff.
but first, i'm not sure about this line:

define('XOOPS_DB_HOST', 'localhost,1433');

i guess XOOPS keeps blind about the server address string and to include the port is not any kind of a problem.

i'll begin and carry out basic tests of MSSQL connection from xoops... and - of course - keep you all in touch about that

jerome.

I'm currently having some problems converting MySQL DB to MSSQL one... on some tables i got syntax error on the scheme generated by Enterprise Manager (i use this tool, feature "import data", to convert)

someone told me MSSQL was kind of deprecated and i'd rather use ODBC to discuss with MSSQL server

no feedbacks up to this point?

jerome.

So whats your progress on this project?
I to need it to work with mssql, but am finding it very difficult even to get it to connect. or what to change.