Hi Judy,

That's pretty much how I thought things worked. I already listed about a dozen things since creating that new directory at Pair.com (already shipped a few). What I was concerned about was relists. AW makes a copy of the original image and stores its info in one of the Images files in the Database (I can't find an Images folder, so the data must be in the Images.MB file), so even if we delete or change the original image file, we can still relist the Lot.

When we relist a Lot, AW drags out, figuratively speaking, that old image and reuses it. In other words, if we were certain the old image was still in the AW database, I suppose we could relist the Lot without re-uploading the images as long as that Profile pointed to the original directory online. Or would we have to re-upload to get the datestamp file updated??? Well, that's a bit off-topic. What I was worried about was that for a relist, AW would pull up the old image info, and let's say its LotImg number is 12345. And let's also say there's another LotImg number 12345 in the database from when it was out of synch. Ok, wait! There can't be another LotImg 12345 because two files can't have the same name, but these aren't really files -- the info is just code (?) within a larger file (? ? ?), so maybe two images can have the same LotImg numbers. Stop me -- I have no idea what I'm talking about........

Maybe the real question is: Are images named locally or not until they arrive at the remote host?

When the database was out of synch (actually, it still is; it just doesn't matter for new Lots as long as I upload to the new directory), how exactly did AW get confused? I think the answer to this question is either very simple and I'm just not seeing it, or it's very complicated and would take an hour to explain and first I'd have to understand how the Borland database works.

Sue