Thanks Will,
to avoid further misunderstandings -
the escape"feature" of backslash" is fully understood.
The problem is that the 3d party sw or the myODBC
doesn't understand that the inbound text SHOULD HAVE backslash
but does exactly whats expected - escape the next char.
What I'm asking is - is there any configurable way that ODBC can
be made to add that extra escaping backslash needed
other than recompiling ODBC which isn't an option for the moment.
anyone have clue !??
again,
thanx in advance
peter
>>> "Will French" <[EMAIL PROTECTED]> 09/12/01 10:20AM >>>
mySQL sees back slashes ("\") as escape sequence characters. Use either
"\\" or substitute forward slashes ("/").
-----Original Message-----
From: Peter Gad [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 12, 2001 4:10 AM
To: [EMAIL PROTECTED]
Subject: mySQL on unix vs ODBC
Hi everyone !
We've got a problem:
running mySQL on unix(sun) we connect a third party
windows software over ODBC. All is nice until a windows path
is stored in the db
Trying to store "C:\Program Files\3p SW\"
I find that it becomes "C:Program Files3p SW".
Is it possible, by means of configuration, to have backslashes preserved ?
Either in ODBC or ... somewhere ?
Facts:
3d party software = no code no chance of changes
ODBC - installed from myodbc-2.50.37-nt.zip
mySQL - 3.23.39 ( 3.23.41 could be used)
thanx in advance
peter
---------------------------------------------------------------------
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
