Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #13386
| From | "Wolfgang Riedmann" <wriedmann@gmail.com> |
|---|---|
| Newsgroups | comp.lang.clipper.visual-objects |
| Subject | Re: SQL long field names |
| Date | 2021-07-12 16:23 +0200 |
| Message-ID | <il31j9F1ss6U1@mid.individual.net> (permalink) |
| References | <b2294a19-f5b8-44e8-b474-416249d349c7n@googlegroups.com> <ikdreqFu46iU1@mid.individual.net> <3e814551-8cd6-41e6-bc7e-91ebf9ac9029n@googlegroups.com> |
Hi Henry, > An internal array could be a logical idea, until someone changes the > original names of the SQL in the host. Dbs_Alias gave me little > help. After assigning FieldInfo(Dbs_Alias, ...), the next time the > file is opened, the alias has back the field name. of course, this is not a permanent option, so you have to store the aliases somewhere in a persistent manner > Interesting: dbCreate() truncate the original field“s names, and > build a db with few fields which have the same name. the DBF data structure limits the field names to 10 bytes, so changing that in the format would break backwards compatibility. AFAIK FoxPro has done something like this, but they have have an external file with the supplemental informations. Wolfgang --
Back to comp.lang.clipper.visual-objects | Previous | Next — Previous in thread | Find similar | Unroll thread
SQL long field names Henry Fidler <zodcomag@gmail.com> - 2021-07-04 02:39 -0700
Re: SQL long field names "Wolfgang Riedmann" <wriedmann@gmail.com> - 2021-07-04 15:30 +0200
Re: SQL long field names Henry Fidler <zodcomag@gmail.com> - 2021-07-12 03:52 -0700
Re: SQL long field names "Wolfgang Riedmann" <wriedmann@gmail.com> - 2021-07-12 16:23 +0200
csiph-web