Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #12475
| From | D.J.W. van Kooten <vankooten@removethis.ic2.com> |
|---|---|
| Newsgroups | comp.lang.clipper.visual-objects |
| Subject | Collation problem |
| Date | 2019-05-10 09:05 +0200 |
| Organization | IC2 |
| Message-ID | <qn7adepmhk5d3mcbspf2c19bss43bjem7n@4ax.com> (permalink) |
For years our programs start somewhere with SetCollation(#Windows). One of the databases contains a string (used to be a constant) being looked up after which the approriate translation is returned. Suddenly one of our clients saw some (not all) of their captions, texts remain untranslated (it then either shows the "constant" or a default which is usually English - this is beging logged. It searches something like FX_NAME. When I search in e.g. dbMax I can't indeed find these data either. But when I do that on my own system it works fine. This is 100% the same DBF/CDX (I retransferred dbf/cdxto the client to be sure). What did solve it for now in dbMax : Settings, tab database, collation Clipper DOS [US ASCII] and then reindex. Client is in Canada on Server 2012 R2. Nothing seems to have changed in either my code, the DBF, or the environment. DBF is ANSI. What can explain the very same DBF/CDX not to find these "FX_ keys with the same program settings while it did before and it does again if reindexed with Clipper collation? Dick
Back to comp.lang.clipper.visual-objects | Previous | Next — Next in thread | Find similar | Unroll thread
Collation problem D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2019-05-10 09:05 +0200
Re: Collation problem Johan Nel <johan.nel@xsinet.co.za> - 2019-05-10 11:25 +0200
Re: Collation problem D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2019-05-10 12:30 +0200
Re: Collation problem Johan Nel <johan.nel@xsinet.co.za> - 2019-05-10 13:36 +0200
Re: Collation problem D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2019-05-10 16:56 +0200
Re: Collation problem "Jamal" <noooospam@example.com> - 2019-05-11 04:32 -0400
csiph-web