Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #12475 > unrolled thread
| Started by | D.J.W. van Kooten <vankooten@removethis.ic2.com> |
|---|---|
| First post | 2019-05-10 09:05 +0200 |
| Last post | 2019-05-11 04:32 -0400 |
| Articles | 6 — 3 participants |
Back to article view | Back to comp.lang.clipper.visual-objects
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
| From | D.J.W. van Kooten <vankooten@removethis.ic2.com> |
|---|---|
| Date | 2019-05-10 09:05 +0200 |
| Subject | Collation problem |
| Message-ID | <qn7adepmhk5d3mcbspf2c19bss43bjem7n@4ax.com> |
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
[toc] | [next] | [standalone]
| From | Johan Nel <johan.nel@xsinet.co.za> |
|---|---|
| Date | 2019-05-10 11:25 +0200 |
| Message-ID | <qb3g1q$4ch$1@dont-email.me> |
| In reply to | #12475 |
Hi Dick, You sure there was not a "Reindex" task outside your application that happened? Remember the difference between Clipper and Ansi/Windows Collation will have the "_" be handled as First/Last in sorting, hence if your application assume it is the wrong one, you will end up with some "keys" not found. On 2019/05/10 09:05, D.J.W. van Kooten wrote: > 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 -- *Johan Nel* FOX member : Friend(s) of XSharp X# Website : https://xsharp.info X# Forums : https://xsharp.info George, South Africa
[toc] | [prev] | [next] | [standalone]
| From | D.J.W. van Kooten <vankooten@removethis.ic2.com> |
|---|---|
| Date | 2019-05-10 12:30 +0200 |
| Message-ID | <rekadedgpgrpct8e2pqc2tksm082nqpdpg@4ax.com> |
| In reply to | #12480 |
Replying on message of Fri, 10 May 2019 11:25:14 +0200 from Johan Nel: Hello Johan Nel >You sure there was not a "Reindex" task outside your application that >happened? Remember the difference between Clipper and Ansi/Windows >Collation will have the "_" be handled as First/Last in sorting, hence >if your application assume it is the wrong one, you will end up with >some "keys" not found. Thanks for reminding me to the differences between those 2 collations. Yes I am sure about not reindexing but the weirdest thing is that when I use e.g. dbvMax (or my applications of course) to locate FX_SOMETHING it will be found. When I send the same DBF+CDX to the server of my client it is NOT found unless I reindex in dbMax with Clipper DOS Collation. It should find the key in both cases even though the collation would cause a different presentation order. And it should certainly not stop finding it when I transfer it (using Explorer \\tsclient) to their RD accessible server... Dick
[toc] | [prev] | [next] | [standalone]
| From | Johan Nel <johan.nel@xsinet.co.za> |
|---|---|
| Date | 2019-05-10 13:36 +0200 |
| Message-ID | <qb3nnj$df7$1@dont-email.me> |
| In reply to | #12482 |
Hi Dick, Ok I am not an expert on it, but are there not a server setting on their side that changes the Collatioon to the DBFCDX in Ansi and not Clipper collation format? On 2019/05/10 12:30, D.J.W. van Kooten wrote: > Replying on message of Fri, 10 May 2019 11:25:14 +0200 from Johan Nel: > > > Hello Johan Nel > >> You sure there was not a "Reindex" task outside your application that >> happened? Remember the difference between Clipper and Ansi/Windows >> Collation will have the "_" be handled as First/Last in sorting, hence >> if your application assume it is the wrong one, you will end up with >> some "keys" not found. > Thanks for reminding me to the differences between those 2 collations. > > Yes I am sure about not reindexing but the weirdest thing is that when > I use e.g. dbvMax (or my applications of course) to locate > FX_SOMETHING it will be found. When I send the same DBF+CDX to the > server of my client it is NOT found unless I reindex in dbMax with > Clipper DOS Collation. > > It should find the key in both cases even though the collation would > cause a different presentation order. And it should certainly not stop > finding it when I transfer it (using Explorer \\tsclient) to their RD > accessible server... > > > Dick -- *Johan Nel* FOX member : Friend(s) of XSharp X# Website : https://xsharp.info X# Forums : https://xsharp.info George, South Africa
[toc] | [prev] | [next] | [standalone]
| From | D.J.W. van Kooten <vankooten@removethis.ic2.com> |
|---|---|
| Date | 2019-05-10 16:56 +0200 |
| Message-ID | <g44bdep8h55e26iqmnieoo0rmh273birs3@4ax.com> |
| In reply to | #12485 |
Replying on message of Fri, 10 May 2019 13:36:19 +0200 from Johan Nel: Hello Johan, >Ok I am not an expert on it, but are there not a server setting on their >side that changes the Collatioon to the DBFCDX in Ansi and not Clipper >collation format? That's higly unlikely. On the other hand it's difficult to find what else the cause could be. I checked the same file for another client (USA) which gave the same problem. A perfectly working dbf+cdx here where lookups fail once transferred to the clients server unless I reindex them with dbMax DOS Clipper collation on. Dick
[toc] | [prev] | [next] | [standalone]
| From | "Jamal" <noooospam@example.com> |
|---|---|
| Date | 2019-05-11 04:32 -0400 |
| Message-ID | <qb61bp$vlg$1@news.albasani.net> |
| In reply to | #12486 |
I am in the US, can you post the dbf an cdx to the X# forum and I'll take look? Will discuss further there. Jamal "D.J.W. van Kooten" wrote in message news:g44bdep8h55e26iqmnieoo0rmh273birs3@4ax.com... Replying on message of Fri, 10 May 2019 13:36:19 +0200 from Johan Nel: Hello Johan, >Ok I am not an expert on it, but are there not a server setting on their >side that changes the Collatioon to the DBFCDX in Ansi and not Clipper >collation format? That's higly unlikely. On the other hand it's difficult to find what else the cause could be. I checked the same file for another client (USA) which gave the same problem. A perfectly working dbf+cdx here where lookups fail once transferred to the clients server unless I reindex them with dbMax DOS Clipper collation on. Dick
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.clipper.visual-objects
csiph-web