slxdeveloper.com Community Forums

The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!

External Development Forums - SalesLogix OLEDB Provider
Forum to discuss using the SalesLogix OLE DB Provider from external applications (including usage of built-in provider procedures). View the code of conduct for posting guidelines.

Forums RSS Feed

Back to Forum List | Back to SalesLogix OLEDB Provider | New Thread

View: Search:

Author

Thread: Two Byte Characters via SLXOLEDB conn - WorkAround?!

Carla Tillman
Posts: 290

Two Byte Characters via SLXOLEDB conn - WorkAround?! Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 01 Jun 07 2:41 AM

Hi,

I'm trying to push Japanese characters through the Provider from a website (*.asp). Previously these were pushed (via standard oledb conn) by using the N prefix for literal storage.

Example:
SQL = " 'UPDATE myTable SET myField = N' " & myInputBoxOnTheASP & " ' "

The Provider chokes on the N prefix and I haven't found a suitable workaround.

What are you folks doing to pass UniCode through the Provider - from outside of the application?

Note: The fields are nVarChar & nText. It is long standing table/fields with quite a bit of Japanese currently stored and retreived without issue. Input via the Provider is the problem d'jour.

SLX v7.01

SQL2005

Server 2003

IIS 6

Carla

[Reply][Quote]

Ryan Farley
Posts: 2265

Re: Two Byte Characters via SLXOLEDB conn - WorkAround?! Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 01 Jun 07 1:00 PM

Hello Carla!

The problem is likely due to the formation of the string and passing that into the provider via ADO. What I would suggest is to use one of the following methods, instead of a SQL statement string, and you'll likely have much more success:

1) Use a parameterized query. Then you can set the parameter values as needed with the double-byte char strings. See http://www.slxdeveloper.com/page.aspx?action=viewarticle&articleid=51 for an example (you don't necessarily need to prepare the query, it does show an example of using parameters however).

2) Use an updateable recordset. See an example here: http://www.slxdeveloper.com/page.aspx?action=viewarticle&articleid=76

Make sense?

-Ryan

[Reply][Quote]

Carla Tillman
Posts: 290

Re: Two Byte Characters via SLXOLEDB conn - WorkAround?! Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 03 Jun 07 5:08 PM

Hi ya Ryan!

Hey thanks for the suggestions. I gave both of these a shot; both were a "No-Go".

Once it hits the SLXOLEDB - it gives the error:
"SalesLogix OLE DB Provider error '8004277a' Failed to parse SQL."

The SQL statments will run fine if I put them through SQL Management Interface. I also tried passing standard English with the N prefix with the same results. It just doesn't like the literal (N).

Any other ideas? The only other idea I can come up with is bypassing the Provider, and I REALLY don't want to set that particular precedence.

c

[Reply][Quote]

Page 1 of 1

You can subscribe to receive a daily forum digest in your user profile. View the site code of conduct for posting guidelines.

Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!

slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation. This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.	code of conduct \|

page cache (param): 11/26/2024 6:46:55 AM