Bob,
Thank you VERY much for the insight. I really need some help resolving this
problem. However....
> Volume Corruption
On one file only? I suppose that possible, but I think it's pretty unlikely.
> File was not saved where you thought it was saved.
Then why would the original file have been deleted?
> User or app appears to have saved the file but in reality, didn't.
Again, why would the original file have been deleted?
-Dan
On Jun 2, 2010, at 10:00 AM, use-revolution-requ...@lists.runrev.com wrote:
> Too little information. I can think of at least one way: Volume Corruption. I
> can think of another way: File was not saved where you thought it was saved.
> Yet another way: User or app appears to have saved the file but in reality,
> didn't.
>
> Bob
>
>
> On Jun 2, 2010, at 9:02 AM, Dan Friedman wrote:
>
>> Hey...
>>
>> I am writing compressed XML data to file on a server using the put command.
>> Every now and then, I get a report from a user that when they go to read the
>> data, they are getting an error. When I look on the server, the file is
>> gone! Not empty, not zero K... just gone - nonexistent!
>>
>> Let's assume for a moment that the file was there to begin with, and there
>> is no one messing with the data and secretly deleting things. It must be
>> something in my app that is causing this. But, what could it be? Nowhere
>> am I deleting a file.
>>
>> Can anyone think of a way you could delete a file without actually deleting
>> it?
>>
>> I tried:
>>
>> put compress("") into url x
>>
>> I thought that compressing "empty" might do something funny. But it didn't,
>> it just wrote some gargly-goop.
>>
>>
>> ANY thoughts out there??
>>
>> Thank you in advance,
>> Dan
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
