I just realized something... shouldn't the Flood Check (mine's set at 10 seconds) prevent accidental double-postings? I'm only asking because apparently it doesn't. Or is the nature of double-postings themselves outside the scope of the software (if that makes sense)?

I think what happens is a double click actually gets two instances of the program going at once. So, it's a bit of a race. If both are running at the same time, the floodcheck gets missed because the first one hasn't actually been committed yet.

I think the only "real" way around this is to maybe do some javascript. So, you click the submit button, and then maybe the button gets disabled by javascript.

I love seeing the disabled submit buttons, so it'd be kinda cool to get it in to stop it ;)...

This is probably going to end up waiting until 7.1. I need to add the ability to specify a javascript unload statement in the header. Otherwise if you hit submit and encounter an error, the button is still disabled when you go back So, I have to rework things quite a bit and don't want to do that on a minor release.

Worth the wait! Thanks!