Ask a Question related to Coldfusion Database Access, Design and Development.
-
doramon #1
cfqueryparam unicode characters
I am storing Unicode characters in sqlserver.
If I use :
SELECT * table values WHERE a=N"#val1#" it works fine.
However if I use:
SELECT * table values WHERE a=<cfqueryparam value=N"#val1#"
cfsqltype="cf_sql_varchar">
I get the following error:
Invalid token '"' found on line 16 at column 51.
The CFML compiler was processing:
a cfqueryparam tag beginning on line 16, column 31.
a cfqueryparam tag beginning on line 16, column 31.
Can someone please help?
doramon Guest
-
AxAcroPDF LoadFile contains Unicode (CJK) characters
I'm using AcroPDF.dll version 9.0 in my C#.Net Windows Forms application. I initialize an instance of the Adobe control, and use the LoadFile method... -
Unicode characters from DB2 using JDBC in ColdFusion MX7
JDBC driver from ColdFusion MX 7 does not return Unicode characters to me. I create data sources for one Unicode DB2 7.2 database -- one for direct... -
Unicode characters above FFFF
How can I generate/display on a page/ Unicode characters based on unicode scalar values? I know ColdFusion function chr() works very good for... -
Unicode characters and ado.
I have an Access 2002 database which stores unicode characters. I am using adodb.recordset object to display these fields on a web page. If I were... -
entering unicode characters
I would really appreciate some help with this. I am using mozilla (1.2.1) with XFree86 (3.3.6). How can I enter a unicode character into mozilla? -
PaulH #2
Re: cfqueryparam unicode characters
lose the unicode hinting (N') and read [url]http://www.sustainablegis.com/blog/cfg11n/index.cfm?mode=entry&entry=F9553D86-20ED-7DEE-2A913AFD8651643F[/url].
PaulH Guest
-
doramon #3
Re: cfqueryparam unicode characters
Great! Now I don't need 1 set of code for MS Access and another for SQL Server. Thanks Paul for pointing this out.
doramon Guest
-
PaulH #4
Re: cfqueryparam unicode characters
well if you do that you're probably missing out on some of the goodies that sql
server has to offer that access doesn't (or does in a limited way). stored
procedures, triggers, identities, full-text indexing, etc. all can really power
up db interactions.
PaulH Guest



Reply With Quote

