I don't know the reason (perhaps OS-based, since tables are implemented as eponymous files), but it was a pretty awful idea to allow special chars in names in the first place. you probably have only two options, equally unpleasant: - rename your tables and columns - back-tick all your non-standard names in queries: `négociateurs`.`téléphone`... (not even sure it will work, and don't want to try...) Good luck (BTW there is a similar problem with your e-mail name!! "EKSTEIN, Clément @ Paris" translates as "EKSTEIN; Clément @ Paris" in the "To" with Outlook Express, causing a failure to answer...) Stick to standards. EQCA Ignatius _________________________ ----- Original Message ----- From: "EKSTEIN, Clément @ Paris" <clement.ekstein@cbre.com> To: <php-db@lists.php.net> Sent: Wednesday, August 06, 2003 11:46 AM Subject: mssql and Apache 1.3.28 and Win2k > I'm not shure that's a pure PHP bug, the problem only occur since > I've ugraded Apache to 1.3.28. > > All SQL queries containing tables or column names containing special chars > (ie: > e) fails with the following PHP error message : "mssql_query(): message: > Invalid object name 'Negociateurs'. (severity 16)". > > I've tested few PHP 4.3.X versions with previous Apache releases and it > works > so I think the problem is comming from the 1.3.28 version and PHP module. > > I'm runing Win2k SP4, MSSQL 2K. > > Regards > Clement > > -- > PHP Database Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
