> Plus its always worth putting a cfabort after your > cflocation, just to be sure that CF doesn't even bother > trying to process anything after the cflocation.
I tried that and it didn't change anything. Also, it seems very silly to have to do that. Surely it would be a "bug" if any code was run after the cflocation. Paul -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
