>Look into the KB here on UT, FAQ section, WIN32API & others APIs category. >There are two FAQs on how to convert and send Unicode strings in VFP. > >Vlad > >>BTW, has anyone found a way to send Unicode string from VFP into >>any Office 97 app? I'd be happy to do the conversion from 1250 or >>1251 into Unicode from within VFP, and not to write those ugly >>macros within Excel and Word. Took a look at it, and it probably works with Win32 API, but Word97 won't take it - it expects that an OLE user doesn't speak Unicode, but forcibly tries to interpret the string it gets as single-byted (single-bytten?). If I translate to double-byte and then to unicode using strconv(strconv(string,1),5), it accepts only the first character, since in unicode the next byte is null, and it thinks it's the string terminator. So OK then, I wrote the macro. Now I'd like to run that macro from VFP before doing anything else (i.e. before switching into Word or Excel), but yet haven't found a way to find it. Tried w_go.normal.macros.to_uni(), w_go.macros.to_uni(), w_go.normal.to_uni(), w_go.to_uni() - and many other combinations, but can't find the way to do it yet. I'd be much relieved if someone gave me a hint. BTW, I've found several functions having xxxxC (like ChrTranC()) which are supposed to deal with double-byte chars, yet there's no way of dealing with double-byte strings in many other situations (i.e. can't have a textbox with .Unicode or .DoubleByte property), so it seems that we must program workarounds for all situations like this. Will VFP6.0 have finally Unicode?