jim said:

Sorry, I do not keep track of what you have done in the past

well, gee, but then you say "it didn't work." how about saying something at the time? especially if you're not gonna "keep track"?

if it fails I delete it and move on.

that doesn't help you _or_ the programmer.

In the future if your stuff does not work, I will tell you, but I notice that when I tell you that something does not work, you are not receptive to that information

i don't see how asking for details is being "not receptive". nor do i see how an offer to troubleshoot the problem can be seen as being anything _except_ "receptive"... but you didn't tell me which program you looked at, or how it didn't work, or say _anything_ specific at all. so exactly how _should_ a programmer react to that?

but rather blame the user

nobody blamed any user, for anything.

or suggest a workaround

where was a workaround suggested?

without acknowledging that what you are suggesting is a workaround.

again, where was a workaround suggested? for what? you keep saying things that _imply_ some shortcoming, but you never actually describe any actual shortcoming. so, again, how specifically do you think i should react? -bowerbird