Hi,
I've got A5 V4.5 and two very simple tables. 15 or so fields and a couple thousand records in each. Easy field rules, few saved operations, couple indexes, no xbasic. Can't get much simpler.
I want to export some of the fields to a simple text file; open in word processor, a little editing, and print it. But I don't want all of each field.
Since A5 won't export calculated fields, I tried to add a new character field, length 80, to each table. Figured I'd do an update to populate it, then export that field. The restructure seemed to go OK, nothing in the Violated table, but when I looked at the result, my memo fields were corrupt. Some were with the wrong record, others were truncated from the front, others were missing, and some were fine.
I worked around it by creating a new, empty, table with same fields plus the new field. Restored the first table from my backup program and appended the records to the new table. Did the update to populate the new field, changed it to a calculated field so it will fill in automatically with any new records, created an export operation, ran it and got what I wanted.
Why couldn't I add a field to the original tables? I believe the usual thing to watch out for in such a case is a corrupt record, but if I append all records to a new table, am I not appending the corrupt record as well? I guess I can't be, because the new table works.
Any ideas? I'm stumped!
Thanks,
Gary
I've got A5 V4.5 and two very simple tables. 15 or so fields and a couple thousand records in each. Easy field rules, few saved operations, couple indexes, no xbasic. Can't get much simpler.
I want to export some of the fields to a simple text file; open in word processor, a little editing, and print it. But I don't want all of each field.
Since A5 won't export calculated fields, I tried to add a new character field, length 80, to each table. Figured I'd do an update to populate it, then export that field. The restructure seemed to go OK, nothing in the Violated table, but when I looked at the result, my memo fields were corrupt. Some were with the wrong record, others were truncated from the front, others were missing, and some were fine.
I worked around it by creating a new, empty, table with same fields plus the new field. Restored the first table from my backup program and appended the records to the new table. Did the update to populate the new field, changed it to a calculated field so it will fill in automatically with any new records, created an export operation, ran it and got what I wanted.
Why couldn't I add a field to the original tables? I believe the usual thing to watch out for in such a case is a corrupt record, but if I append all records to a new table, am I not appending the corrupt record as well? I guess I can't be, because the new table works.
Any ideas? I'm stumped!
Thanks,
Gary
Comment