> quick responses as always. Any way of working around it that comes > to mind? None I would suggest at this point given that the bug was fixed. This behavior is exactly what V4 did, so I have a hard time believing that's not relevant. Old jars perhaps corrupting things. -- Scott