I have to tell you that nothing has changed between the piece of code that is kicking this error off and this piece of code. Please tell me what the heck has happened here as I am most frustrated.
On one level, by posting no code you've given us little to work with.
On another level--the wetware level--you've given us plenty.
If you approach this problem with the attitude of "but nothing has changed!" you are setting yourself up. It's a bug in your thinking. Things change. It's a fundamental law.
- Clocks tick onward. When the date changes code might be taking alternate paths.
- Underlying data changes, causing code to take alternate paths.
- The environment changes, often by someone installing (or uninstalling) software or service packs (or Perl modules). Or permission bits get flipped, or disks fill up.
Accept that something has changed, and get on with finding out what that something is. And yes, that can be frustrating, but it's a probably a learning opportunity (even if it is an ill-timed one).
A useful exercise in cases like this is to try to distill the problem down to a small example that strips out extraneous detail. By the time you're there, the problem is liable to be apparent. If it isn't, you'll have a clean snippet to post.
| [reply] |
You've provided absolutely no information here. What's in "this piece of code"? Which is the "piece of code that is kicking this error off"? It's clear you're frustrated, but without giving some information, there's no way anyone could help.
Gather some information, then post a more coherent writeup, and we'll go from there.
| [reply] |
I did not post this, someone must have done this without my knowing. I am not this crazy...
peace, LOVE and ((code))
basicdez
| [reply] |
well, the error message was certainly instructive, now if you could only post the code which is generating the error message, it would be certainly helpful :-) | [reply] |
