D3 Accented Characters and Code Pages

#11

Hi Grigory,

Thanks for your exhaustive spec. It's as impressive as well. Me, not being
an expert in these affairs to such a degree I would only admit that I always
try to limit my efforts to the boundaries of both the task attainability and
the client's budget. So that I never took my dive that deep.

Cheers,
Nick

"GVP" <gvp (AT) infotools (DOT) ru> wrote

Quote:

Hello Nick,
Nice to see You.

LCMapString is more useful. For convert MB string to WideChar (Unicode)
MultiByteToWideChar && WideCharToMultiByte API or StrConv(Str,
vbFromUnicode) in VB

LCMapString
The LCMapString function either maps an input character string to
another using a specified transformation or generates a sort key for
the input string.

int LCMapString(
LCID Locale, // locale identifier
DWORD dwMapFlags, // mapping transformation type
LPCTSTR lpSrcStr, // source string
int cchSrc, // number of characters in source string
LPTSTR lpDestStr, // destination buffer
int cchDest // size of destination buffer
);
snip

#12

Rick,

"Rick Smereka" <rick_smereka (AT) yahoo (DOT) com> wrote

Quote:

I performed an experiment. I created a BASIC subroutine which converts
from CP437 to CP1252 and modified attribute 7 of a copied dictionary
item (last name attribute) to call this subroutine.

Attr 7 won't ever work as long as it doesn't change any data stored in an
item! Try attr 8 instead.

Another idea. Create a "mirror" file for your file in question. Then write a
CALLX type trigger, where you implement CONVERSE your chars from 437 to
1252. Then you've done. TOUCH command will make translated file for you for
the first time.

HTH
Nick

When I produce a

Quote:

report on the D3 side into a hold file and then copy that report to
Windows and view it in a Windows editor, the translation is successful.
When I pull the data into Excel using ODBC, the data does not display
correctly. I need to find a hex dump program so that I can look at the
file byte by byte and see if the data is being mangled by the ODBC
server or the data is in tact an Windows is refusing to display it
correctly. Also, when I import the D3 report into Excel (fixed field),
Excel asks for the 'file origin'. If I use Windows/ANSI (which I assume
is CP1252) or CP1252, the report displays correctly in Excel but this
again is from a D3 report simply copied.

BTW I am using the Wikipedia CP1252 web page as my reference.

I'll report back once I examine the files on the byte level

Rick

#13

Ross,

"Ross Ferris" <rossf (AT) stamina (DOT) com.au> wrote

Quote:

I believe there may be "issues" with running under VMWare, or any of
the other virtualization environments, as part of what your activation
code runs off is the NIC, and even a reboot of the VM may cause "havoc"
as the software emulation may provide a different/new identifier

It's never been a problem. VMWare assigns a unique and permanent identifier
for each VM stored in the host. As fas as VMWare provides an exceptionally
limited variety of virtual hardware drivers, chances for license to be lost
are even much lees than running D3 in a real hardware environment.

Quote:

You can also get the same sort of problems/issues if you are hooked up
to a SAN and go & move things about I believe

VMWare dosn't know anything about SAN, etc. whilst OS takes care of all this
hassle.

Nick

#14

Nick,

Nikolai Lukin wrote:

Quote:

Attr 7 won't ever work as long as it doesn't change any data stored in an
item! Try attr 8 instead.

I kind of figured that out when the output conversion was not working
from ODBC. Strange though, when doing an Access report in D3, the
conversion was occurring.

Quote:

Another idea. Create a "mirror" file for your file in question. Then write a
CALLX type trigger, where you implement CONVERSE your chars from 437 to
1252. Then you've done. TOUCH command will make translated file for you for
the first time.

I kind of bumped into this when I was reading Chapter 7 of the D3 SQL
Users Manual where it talks about triggers. Thinking that this was an
excellent way to implement a global conversion, I gave it a try.
Unfortunately, the files I am using are actually Q-pointers to another
account and I found out that there is no file-defining correlative when
the file is a Q-pointer (at least that option is not available when I
use 'ud' to update the item).

You lost me in your explaination. What is a 'mirror file' and how does
it differ to a Q-poiinter? Also what is 'CONVERSE' and 'TOUCH'?

Rick

#15

Rick,

"Rick Smereka" <rick_smereka (AT) yahoo (DOT) com> wrote

Quote:

Another idea. Create a "mirror" file for your file in question. Then
write a
CALLX type trigger, where you implement CONVERSE your chars from 437 to
1252. Then you've done. TOUCH command will make translated file for you
for
the first time.

I kind of bumped into this when I was reading Chapter 7 of the D3 SQL
Users Manual where it talks about triggers.

I didn't mean SQL triggers, but CALLX triggers. See RefMan D3 7.5 page 818.

Quote:

Unfortunately, the files I am using are actually Q-pointers to another
account and I found out that there is no file-defining correlative when
the file is a Q-pointer (at least that option is not available when I
use 'ud' to update the item).

Suppose, you have:

thisaccountfile

01 q
02 thataccount
03 thataccountfile

Then you can access corresponding DATA section D-pointer using
ud thisaccountfile thataccountfile

Quote:

You lost me in your explaination. What is a 'mirror file' and how does
it differ to a Q-poiinter? Also what is 'CONVERSE' and 'TOUCH'?

Sorry, I meant CONVERT, again, RTFM, same RefMan, page 281.
For TOUCH see page 1392.

HTH,
Nick

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

D3 Accented Characters and Code Pages

comp.databases.pick comp.databases.pick

Re: D3 Accented Characters and Code Pages - 09-15-2006 , 07:42 AM

Re: D3 Accented Characters and Code Pages - 09-15-2006 , 07:48 AM

Re: D3 Accented Characters and Code Pages - 09-15-2006 , 07:54 AM

Re: D3 Accented Characters and Code Pages - 09-15-2006 , 04:01 PM

Re: D3 Accented Characters and Code Pages - 09-18-2006 , 11:39 PM