Quote:


The field names contain numbers but there is probably a record in your Q&A database that has the data "____" in those fields. The errors are telling you that it is clearing those fields rather than have the junk data in them

Quote:

This sounds like a perfect example of a Q&A database that should be broken into subforms.  It sounds like you have all these pages for line items on the invoice.  Each of these lines should really be a separate record in their own database.  shown as a sub form to the Invoice form.  The other 138 fields are probably associated with the Invoice "header", common to all line items on the invoice.

I would even suggest you might want to do the redesign in Q&A before translating to Sesame. Make copies and work on the copies only.  It will take some effort, but make a new InvItems database, and be sure to use a Unique field for each record, most likely the Invoice number.  Copy the Invoice Number and all the info on line 1, for all the records with info on line 1 to the new database, then copy the Invoice Number and all info on line 2 for all the records with info on line 2, etc.  Do this for all 51 lines.  Now delete all 51 lines from this database and all you should have are the 138 remaining fields which will be the Invoice Header.

Now when translating into Sesame, bring both Q&A databases into the Invoice.db application.  Bring in only the Header information to the InvHeader database and bring in InvItems into the InvItems database.  Then make the InvItems a subform for Invoices form that shows the InvHeader information, linked by the Invoice Number field to show the InvItems records.

Note, the suggestions are a concept only, and the specifics may need to be altered based on the contents if the Q&A  records.  Example, maybe you can't use Invoice number as the common field, maybe you need something different like data and/ or time and/or record and/or Customer's PO, etc.

Erika wrote Quote:

Something that worked for me was to simply export all the info from all the fields in the Q&A DTF at once, into one export file. Then I selectively imported from that file with mutiple imports using [Ignore Column] repeatedly so that I could pluck just the fields I wanted on each pass.

This saved me from manually editing in Notepad.

(Hope I didn't forget something, it's late and I'm pulling this from memory out of a very sleepy brain. )

Quote:


You could, but you would need to do some pretty hefty munging of your header and line items files to get them into a single file of the correct format for the hierarchical import. If you do the relational link, then export the data from Sesame, it will create the hierarchical import file for you. You can then switch to natural links, import the exported file, and you're good to go.