Hi -

I'm having a horrible time with my export/import although I have had one or two "semi-successful" imports.  

On my last attempt, I was told that "Import reports 1 error lines from ASCII file (.. path .. filename) - Check the administrative log for deails."

OK - I give up - lol - where, please, is the Administrative Log?  Thanks!

     - Spencer

Thanks Ray -

I must have missed it when I read the secton on Imports.  I had looked in the index but didn't find any reference to Administrative Log.

The manual reference is helpful.

Unfortunately, the log wasn't.   lol

Ray -

DURN!!!!

You got here before I could modify my last reply.  lol  Actually, I was never reading the whole line.  I tried resizing the box and couldn't, tried all other kinds of crazy things and gave up, thinking the rest of the line must just not be important.

Once I found the simple - fairly standard - (I'm so embarrassed - lol) "right arrow" and scrolled to read the rest of it, it gave me the info I needed.

I assumed that if there were too few fields in the import file, Sesame would just import what was there.  Apparently, it is looking for the same number of fields, identified in the import spec.  Very nice.  And, now, I adjusted the number of fields and IT WOIKED!!!!

Actually, my problem was that I was uncertain how to tell in what order the data would be imported.  So, rather than keep struggling with that problem, I just created an ASCII text file to hold the values 1 through (now) 67 .... the number of fields in my database.  Now I have a record where each field is numbered for the import order. 

Hopefully, that will make it easier for me to set up the export file correctly.

Thanks!

     - Spencer

You could also create a single record export file from Sesame, WITH FIELD NAME HEADER, and use that header line as a list to read when setting up the export field positions in Access or whatever other program you are exporting from.