test please delete

[voodooflux]

Nearly as bad as using the W word.

Hmmm, good point. Maybe I should have *'d it out

[HeliCraig]

Nice shade of blusher that.

Can I have it back when you are finished?

[zeitghost]

Ahem, any bonus points for two in a row?

[TheFaQQer]

SPACE INVADERS


...........................................................................................
.............
...........................................................................................
.............
...........................................................................................
.............
...........................................................................................
.............
...........................................................................................
.............
.............

...........................................................................................

.............
.............
.............

Very pretty

[TheFaQQer]

Oh FFS... I give up.

We have a piece of code which can receive a nasty reply from SQL (deadlock), and it turns out the first thing which the error handler tries to do is close the recordset. Recordset not been opened yet, so the error handler fails. Leave connection object to DB open for eternity. Nice.

OfficeIdiots suggestion: Put an "on error resume next" statement in the error handler.


And now you can see why the code was tulipe in the first place. FFS.

How about:

If recordset open THEN close recordset?

Or some such. Looks like it's not an Oracle database, so I don't care.

[zeitghost]

On error del *.*

Works for me...

[voodooflux]

Can I have it back when you are finished?

Yeah, it clashes with my eyeliner anyway.

[HeliCraig]

How about:

If recordset open THEN close recordset?

Or some such. Looks like it's not an Oracle database, so I don't care.

Really? What a clever idea. Who'd have thought of an If statement. Whatever next.

My god, he is such a numpty idiot. How? Just how?

(Oh, and you're right Faqqer, its MS SQL).

I did take it a step further and suggest that while this would fix the sympton, perhaps he should go and hassle the DBA's to find out why we are getting so many deadlock victim situations when none of our scripts do too much heavy work!! He looked at me gone out. Then did his usual "yes sir, yip, k mate, would look into that aspect today afternoon yesterday please." statement - so I know that'll be fixed then!

[HeliCraig]

On error del *.*

Works for me...

On error kill OfficeIdiot. That would be an improvement.

Yeah, it clashes with my eyeliner anyway.

Which in turn clashes with your stockings.

[voodooflux]

OfficeIdiots suggestion: Put an "on error resume next" statement in the error handler.

He's been hassling me this morning as well with a problem. It was either going to be with:

a) my code
b) his data

Guess which it was.

(Clue: it wasn't 'a').