Now I know that these two camps are notorious for not getting on properly but I'm using the ODBC drivers and everything SHOULD be working.
The wizards in VS.net 2005 are executing queries against the database which look like this:
That's from the ODBC trace file as the queries are generated automagicly by VS. Of course the thing isn't going to work - I'm not certain but I'm pretty sure that putting two periods in there is the wrong sytax. Deos anyone know why this happens or how to stop it?
The easyest thing I've come across so far is to just hack the ODBC driver to filter out the double periods. I've not done that yet because I'm certain there has to be another way.
Someone know's it - I have faith in you all.
Yet another unchecked rambling brought to you by:
Oddball
The wizards in VS.net 2005 are executing queries against the database which look like this:
Code:
devenv 7dc-8b4 ENTER SQLExecDirectW
HSTMT 0FE81FE0
WCHAR * 0x01C4A76C [ -3] "SELECT * FROM `ecommerce`..`addresses`\ 0"
SDWORD -3
devenv 7dc-8b4 EXIT SQLExecDirectW with return code -1 (SQL_ERROR)
HSTMT 0FE81FE0
WCHAR * 0x01C4A76C [ -3] "SELECT * FROM `ecommerce`..`addresses`\ 0"
SDWORD -3
DIAG [23000] You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '.`addresses`' at line 1 (1064)
That's from the ODBC trace file as the queries are generated automagicly by VS. Of course the thing isn't going to work - I'm not certain but I'm pretty sure that putting two periods in there is the wrong sytax. Deos anyone know why this happens or how to stop it?
The easyest thing I've come across so far is to just hack the ODBC driver to filter out the double periods. I've not done that yet because I'm certain there has to be another way.
Someone know's it - I have faith in you all.
Yet another unchecked rambling brought to you by:
Oddball