Hello. Thanks for the suggestions. My country just recently got hit by a typhoon so internet have been out then yesterday I lived trough a costoclondritis attack while on my motorcycle and my right arm was paralyzed. Good thing I was just sitting on the bike with the engine idling or I may have spent more than the 3 hours I cooled down in the hospital yesterday. So there goes my evil plan of buying a Yamaha SRX V-Twin cruiser for my wife. :(
Enough of the side comments (I'm just very happy that it wasn't a heart attack) ... I reviewed the suggestion and my plan will be like this: 1. I have a VMWare Server (if you don't know it, it's a FREE machine virtualization software which you can use to TEST out your software -> http://www.vmware.com/products/server/ ) which I have installed the current system and is upgrading to version 601 from 504. Although this is technically the fastest solution (I hope) ... I do expect that there WILL be some problems when upgrading my client due to hard headedness (If you know what I mean). 2. If step 1 doesn't work, I'll have to try the UTF8 solution by Bill 3. Version 2 - this is the most time consuming. You see, with our version 1 system stable and running ... I am now building version 2 where the significant difference is that all actual MS-SQL manipulation will be done by a C# .NET library and just sending and retrieving data to J. Basically, J will not initiate data update to the sql ... its just going to return result and the C# calling application will have to save the result to the DB. ;) Hehehe. Im a bit perky since yesterday ... near death experience tend to give you a different perspective in life. ;) r/Alex -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of bill_lam Sent: Saturday, September 30, 2006 6:53 PM To: Programming forum Subject: Re: [Jprogramming] Unicode parameter in WD function (J504) Alex Rufon wrote: > I know that everyone should be upgrading to J601 but my client is > running a production system in China and I'm in the Philippines so > updates are a bit tricky. > I agree. It takes one or two days to convert the code, but it takes several months to fully debug and field test. > So here's the problem. I have a VB6 COM DLL which exposes a Function > Returning UNICODE characters from wd is not a problem since all I had to > do was change the code to: > vdata=. u: wd 'olemethod r base executeSQL *', y. > Assume the VB6 COM DLL is written by you, you may convert unicode to/from utf8 vdata=. ucs2 wd 'olemethod r base executeSQL *', utf8 y. u: alone cannot recover returning unicode. you need to change VB DLL to accept utf8 and return utf8. use WideCharToMultiByte and WideCharToMultiByte api to convert between unicode and utf8 -- regards, bill ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
