[Hx] Problem with import/export records.

[D. Wheeler]

I am a “lay” user of Helix Rade for several databases. I currently have two databases that I want to merge into a single, modified database. This entails exporting data from each of the existing databases into the new database. In the new database I created a template identical to the that in the database from which I want to export data into the new database. That is, each field, is identical is terms of type, text or flag. I then selected the View icon used to enter data in the old database and exported those records. The export was in the form of a text file. I then selected the View icon in the new database and selected import and the text file. At that point I get the error message, “Entry incompatible with field type”. I am stumped at this point. Any help will be appreciated.

Running 7.0.3 on a Macbook Pro with OS 10.10.5

[ROGER BILLCLIFFE]

[Originator's address is roge...@mac.com.]


I often (if not always) get this and in my case the import text that is wrong usually includes quotemarks or currency signs, so that might be worth investigating
Roger

> On 22 Nov 2017, at 12:20, D. Wheeler <Hel...@gibhenry.com> wrote:
>
> I am a “lay” user of Helix Rade for several databases. I currently have two databases that I want to merge into a single, modified database. This entails exporting data from each of the existing databases into the new database. In the new database I created a template identical to the that in the database from which I want to export data into the new database. That is, each field, is identical is terms of type, text or flag. I then selected the View icon used to enter data in the old database and exported those records. The export was in the form of a text file. I then selected the View icon in the new database and selected import and the text file. At that point I get the error message, “Entry incompatible with field type”. I am stumped at this point. Any help will be appreciated.
>
> Running 7.0.3 on a Macbook Pro with OS 10.10.5

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

You received this message because you are subscribed to the mailing list <Hel...@gibhenry.com>.
To unsubscribe, send an email <Helix...@gibhenry.com>; to switch to DIGEST mode, send an email to <Helix-L...@gibhenry.com>; to contact a human being, send an email to <Helix-L...@gibhenry.com>.
Google archive since 20 August 2006: http://groups.google.com/group/helix-l.
Basic archive since March 2017: https://gibhenry.com:9100/Lists/Helix-L/List.html

[Gib Henry]

Hmmm…you might want to look into “clipping.”  Unfortunately, the documentation isn’t up to date for version 7 yet, but there is a lot of information available on QSA’s website. 

In a nutshell, clipping structure (e.g. a field, three queries, all the abaci in a relation, or a whole relation) is the easiest way to duplicate stuff, although it might take a little effort to get up to speed.  Once you’re there, it’s the only way to fly.  You can clip structure within a relation, between relations, or between collections.  Many people have “standard” structure such as formatted time stamps, report headers, true/false, etc.  One quick clip, and you have all that pasted into a new relation or a new collection, a real time-saver.

There are probably  tons of other features of Helix that you haven’t yet discovered.  Some might be overkill for you, but some might be really handy and very convenient.  Don’t hesitate to ask here for pointers to get you started.  Cheers,
--
Gib

[Louis]

Check the downloaded text file with Texedit.  You will see what’s wrong 

If you don’t see it right away, download from both database and compare them with a text viewer

Louis

[Louis]

, “Entry incompatible with field type”. I am stumped at this point. Any help will be appreciated.

Running 7.0.3 on

It is usually that.  A different format for a date or number.  

Making a « exactly » same template is not always enough.  Making a template with a format on a rectangle field can be different from the export template ( without specifying the format on a rectangle field will export on the default format of the field) 

Make a quick template in the export database.  Open a second RADE and Copy &paste this template in the import database. 

Even that won’t insure that the default format of the fields are the same. 

You have to check those default format, or push for the format on a rectanglevfirld

TextEdit is your friend

Louis

[Michael S. Scaramella, Esq.]

Dear “D,”

As others have suggested, you need to carefully inspect the exported data files. Instead of TextEdit, I suggest that you use something like Nisus Writer Pro or BBEdit that will display invisible characters and search using GREP. Remember that in Helix, data display and storage formats are independent, with one exception. If you export custom labels for a flag type field, importing the flag values is unforgiving. It is best to export standard flag values such as “Yes” or “1.” The export format can be controlled by setting custom formats for the data rectangles containing flag type fields. Also, remember that abacus values displayed in data rectangles are exported along with field values in data rectangles, but that data values can only be imported into data rectangles containing field icons. That distinction can cause the type of errors you are seeing.

There is something to look for that you probably do not expect is possible. When Helix 7 is exporting large data files, or possibly many smaller data files as controlled by a Sequence, one or more records can be written containing only the record and field delimiters, with the field data values omitted. I have found that data export controlled by Conditional Sequences can trigger inappropriate data validations. Those can trigger erroneous error messages asking if nonexistent data files with missing or nonsensical names should be replaced. Allowing Helix to replace the phantom files allows data export to proceed, but the exported data files have missing data values as I described.

I hope that this helps you to identify the cause of the problems you are experiencing.

Sincerely,

Michael

On Nov 22, 2017, at 7:20 AM, D. Wheeler <Hel...@gibhenry.com> wrote:

I am a “lay” user of Helix Rade for several databases. I currently have two databases that I want to merge into a single, modified database. This entails exporting data from each of the existing databases into the new database. In the new database I created a template identical to the that in the database from which I want to export data into the new database. That is, each field, is identical is terms of type, text or flag. I then selected the View icon used to enter data in the old database and exported those records. The export was in the form of a text file. I then selected the View icon in the new database and selected import and the text file. At that point I get the error message, “Entry incompatible with field type”. I am stumped at this point. Any help will be appreciated.

Running 7.0.3 on a Macbook Pro with OS 10.10.5

<+>-=-<+>-=-<+>-=-<+>-=-<+>-=-<+>-=-<+>

SCARAMELLA & HOOFNAGLE

Computer Division

 ~  *  ~

Voice: 856-424-2100

Web: http://www.ScaraHoof.com

<+>-=-<+>-=-<+>-=-<+>-=-<+>-=-<+>-=-<+>

[D. Wheeler]

Thanks. I solved the export/import issue from one of the databases but now I have encountered another problem. I am working on putting a question together so I can seek further help

[D. Wheeler]

[Originator's address is drwg...@gmail.com.]


Thanks.

Sent from my iPhone

> On Nov 22, 2017, at 7:25 AM, ROGER BILLCLIFFE <Hel...@gibhenry.com> wrote:
>
> [Originator's address is roge...@mac.com.]
>
>
> I often (if not always) get this and in my case the import text that is wrong usually includes quotemarks or currency signs, so that might be worth investigating
> Roger

>> On 22 Nov 2017, at 12:20, D. Wheeler <Hel...@gibhenry.com> wrote:
>>
>> I am a “lay” user of Helix Rade for several databases. I currently have two databases that I want to merge into a single, modified database. This entails exporting data from each of the existing databases into the new database. In the new database I created a template identical to the that in the database from which I want to export data into the new database. That is, each field, is identical is terms of type, text or flag. I then selected the View icon used to enter data in the old database and exported those records. The export was in the form of a text file. I then selected the View icon in the new database and selected import and the text file. At that point I get the error message, “Entry incompatible with field type”. I am stumped at this point. Any help will be appreciated.
>>
>> Running 7.0.3 on a Macbook Pro with OS 10.10.5
>
>

[D. Wheeler]

Thanks, Louis. Got it!

Sent from my iPhone

On Nov 22, 2017, at 7:43 AM, Louis <Hel...@gibhenry.com> wrote:

Check the downloaded text file with Texedit.  You will see what’s wrong 

If you don’t see it right away, download from both database and compare them with a text viewer

Louis

Le 22 nov. 2017 à 07:20, D. Wheeler <Hel...@gibhenry.com> a écrit :

[Lenny Eiger]

On Nov 22, 2017, at 12:19 PM, Michael S. Scaramella, Esq. <Hel...@gibhenry.com> wrote:

Dear “D,”

As others have suggested, you need to carefully inspect the exported data files. Instead of TextEdit, I suggest that you use something like Nisus Writer Pro or BBEdit that will display invisible characters and search using GREP.

I agree with Michael here - BBEdit is wonderful… and its ability to display the “invisibles” is essential.

Remember that in Helix, data display and storage formats are independent, with one exception. If you export custom labels for a flag type field, importing the flag values is unforgiving. It is best to export standard flag values such as “Yes” or “1.” 

It is for this reason I -never- format a flag field at the field level. I format flag input all the time, but its on the template. 

I do format number and fixed point fields to set the number of decimals. I format date fields to specify whether it should include the time or not, etc. 

I would never made a static or dynamic popup at the field level - these are also for the template...

Lenny