If you are referring to the version you suggest to use in your blog, I found another Bug that I mentioned in this thread.
If recycler is turned on this error occurs: "UPDATE statement conflicted with COLUMN FOREIGN KEY constraint 'FK_rb_Modules_rb_Tabs'. The conflict occurred in database 'databasename', table 'rb_Tabs', column 'TabID'."
The stored procedure rb_DeleteModuleToRecycler moves the deleted modules to TabId = 0 to make them vanish from the UI. But in a new installation, TabId 0 does not exist. So the Update fails.
<snip from stored proc>
UPDATE rb_Modules
SET TabID = 0
WHERE ModuleID = @ModuleID
</snip>
Someone to contact John Bowen to fix this ;-)
Cheers Parsley
Well, whenever I'm confused, I just check my underwear. It holds the answer to all the important questions. (Abe Simpson)