Time for a break

[rhosk]

This has got to be the most classic message I've ever received.



Time for a break

[Corey]

Too bad that message wasn't some sort of secret "millionth customer" prize which would have seen you whisked away to Tahiti on a luxury jet. Because that would have been an entirely different kettle of fish.

[rhosk]

Agreed. But, it didn't have to mock me (I think "error" is there 3 times??).

Ye 'ol AMS - lettin' ya' know you got a problem, sir.....

I bet you couldn't duplicate that if you tried

(and don't create a message on the fly either )

[Eagle]

Well I managed to get the same error message the other day, 'wot the...',
(A func I was calling got caught up in a loop, viola.)

Hooray for 'undo' -restore or just real good debugging on my part

[rhosk]

Yep, you nailed it Eagle. That's what I did. Called a func inside a func...I knew it was a mistake, but the error message tickled me. It was like AMS was saying, "I don't know what else to tell ya'", LOL.

[Brett]

Could one of you guys post some script that will make this happen? Perhaps we can look into why there is an error in the error handling and make the message more robust for the future.

[rhosk]

I truly don't think that is was AMS' fault at all. I was "trying" to loop thru a table in a function at the time and it backfired on me. No one in their right mind would use this, but it will give you the message. I can't duplicate what I was originally doing at the time.

function getError()
result = File.Find("C:\\MyDir\\", "*.pdf", false, false, nil, nil);
if result then
--Do something here
else
getError()
end
error = Application.GetLastError();
if (error ~= 0) then
Dialog.Message("Error", _tblErrorMessages[error], MB_OK, MB_ICONEXCLAMATION);
end
end

Ludicrous, I know, but you wanted it

[Eagle]

Yep, 'same dog..different leg action', just plain no worky coding on my part.

I too was looping through a table:

for n, tdat in table do
call another func
end
recall this table func (when I removed this line) Error and Error Message gone.

called the same func inside same func..inappropriately, could'nt finish what it
was doing..I'm glad the Error message came up..stopped the App from crash and burn.