Importing: Sane alternatives to "Last Order"?

[Jeff Albro]

So, I'm working with importing a csv dump from a main frame. Ugly field names.

I want to import them. I can set a custom order, and then pick "last order" next time I import.

But this is a group database, and I've seen the "last order" get screwed up or lost before. I have no idea if it's stored on a per-database or per-user level. And, I can't export a matched list easily for documentation of what goes to what.

I don't trust what I can't verify, and I'd prefer not do adopt the names from the mainframe.

Is there a better option?

Thanks!

-Jeff

[Jeff Albro]

I'd still love an answer to this, but for the mean time, I wrote a python script to change the headers before importing.

It allows me to have a reference csv file that shows the matching field names.

-Jeff

[Lee Smith]

Have you tried crating a script for this import.

Lee

[Jeff Albro]

Yes, but it doesn't seem to keep the custom field matching reliably, and if something goes wrong it's hard to track it down with 256+ fields.

It doesn't keep the matching in the script text itself.

Maybe my problem is that I need to turn off access to editing the scripts to anyone by myself.

-Jeff

[bcooney]

You do not mention how often this import needs to happen. If often, a script, as Lee mentioned, would help speed up the process.

Some trivia on importing that I've picked up from forums. Perhaps someone can chime in to verify:

1. Setting the import file name using a variable changes any matching names setting to last order.

2. Last order can result in mismatched mapping if you've added fields to your tables since you've defined the import mapping.

If there have been changes, I'd import with show dialog setting. Remember to set your next serial numbers.

[Lee Smith]

Do you have different Access, and Privileges set up for these files?

[Jeff Albro]

>>>You do not mention how often this import needs to happen.

Daily.

>>>1. Setting the import file name using a variable changes any matching names setting to last order.

I will keep that in mind.

>>>2. Last order can result in mismatched mapping if you've added fields to your tables since you've defined the import mapping.

That explains ALOT.

I think I will stick with my header renaming script. I know if I "match names" new fields won't matter.

Thanks!

-Jeff