Import from Excel

I’ve been using (or been used by…) this feature for the last few days and have run into some major irritations with it:
( 2.1.1 Win2K Java 1.4.2_04 MySQL 4.018nt)

It doesn’t remember anything from one run to the next (even if you hit back to fix a problem).
Not last directory, window size, repository, field-> column mappings, date format… nada.
This is a real pain when you have an import fail and go back to the
mapping screen and it erases everything (it knows it, but resets it on
entry, except for the date format and repository/table up top).

If an import gets part way through and hits an error, there is no rollback.
Thus, when you fix the problem, you get duplicate rows on the ones that did load the first time.

It doesn’t map the excel sheets to the drop down right.
If I have a file with two sheets, picking sheet A shows the fields for Sheet B (and vice versa).

It ignores calculations: I have a file that uses a lookup to pull the key for a
given row from another sheet in the file. The import shows those cells as
empty. I was able to workaround this by pasting the values to another
sheet, but I consider this a bug.

Can we please get some attention to this area by 2.5 at the latest?
Thanks!

importing will be looked at (and made scriptable) in the next big release.

importing large ammount of data can never be fully rollbacked. DB’s don’t support unlimmited rollback buffers…

jcompagner:
importing will be looked at (and made scriptable) in the next big release.[/quote[
Good! I know that exporting is on the list for the same, which is more important for me. My imports are only for the purpose of migrating from FMP..

importing large ammount of data can never be fully rollbacked. DB’s don’t support unlimmited rollback buffers…

My volumes are small (<2K records); the problem is that there is no feedback on how many records succeeded or ability to have the whole load fail (i.e. rollback). I find that I need to have a database management tool open with “truncate table” ready to go…