I can't search here worth a &^&@ !

Is there an error code generated when the import doesn't have a matching record and comes in as an empty found set?

In short I have a database of books.

I periodically check sales rank and import through XSL 1 at a time.

Sometimes the import doesn't match and the found set is 0... not sure why and can't figure it out...

After painstaking one at a time with pause import I see that even though the found set was 0 there was a matching record and if I go to it and start from there it's fine.

UGH ! Not fine.

This causes the update script to go back to the very first record and start from there.

I have error capture on but can't figure out which code will trigger it... 401 doesn't seem to

Any ideas???

Edited June 21, 200817 yr by Guest

post a copy of your script

Lee

I know I have a lot of strike through's.... but

I have narrowed it to the fact that that the import set is actually empty so there's nothing to import for this record. It's just not in the online database...

So if the import found set is empty how can I set it to preform a find?

Basic script is

copy the isbn into a global field

import records based on the isbn through XSL

go to next record

Would copy if all if I could figure it out but I had 2 hrs sleep last night and am mush !!!

Maybe solved.........

I set in an "if statement" right after the import step

....If [isEmpty (sales rank)] which should be imported through the process...

to trigger a find to keep my place.

Edited June 21, 200817 yr by Guest