174203Re: [magicu-l] v8 to 2.4 Btrieve data conversion
- Mar 7, 2014I understand. After doing the conversion, I was curious to explore the difference.ArchOn Fri, Mar 7, 2014 at 12:03 PM, Andy Jerison <ajerison@...> wrote:
I was suggesting converting the table definition. It shouldn’t be necessary to do anything to the physical table.
Just for the record, the v8 Memo with a:
Picture of 3500, Stored As of String Memo, with a Size of 3502, and a Definition of String
becomes in v2.4:
Alpha with a Picture of 3500, Stored As String Memo, with a Size of 3502.
Unfortunately, it is still not recognizable so you need to go through the conversion as Andy suggested.
On Fri, Mar 7, 2014 at 11:07 AM, Andy Jerison <ajerison@...> wrote:
V9converter can create a project or an export file. If I remember right, if you omit -PROJECT and include -V10EXPORT=MyExportFileName.Ext it will create an xpa-compatible export file with the name you provide. You can then import that file to see the converted table definition.
Thanks, Andy. Where can I find how to convert a single table?
On Fri, Mar 7, 2014 at 10:54 AM, Andy Jerison <ajerison@...> wrote:
The v8 Memo attribute on Btrieve tables is replaced by Alpha of the same size, with the Stored as property set to String Memo. If you export from v8, import to v9, export for 10, convert with v9converter.exe and finally, import to xpa 2.4, you should get that result.
In Magic v8, Btrieve, there is a Memo Attribute that does not exist in Magic v2.4. The table has 4 fields:
1-byte Integer logical
2-byte signed integer
The total record size is displayed as 15 bytes.
I have duplicated the fields in 2.4 with the Memo as a String BLOB. Its size is also 15 bytes. The single, unique index appears identical with the first 3 fields as segments totaling 15 bytes.
Problem is that I get a data definition mismatch. Ideas?
- << Previous post in topic Next post in topic >>