Yup I dooly remember that one. Very hard to forget it. What I really don't understand is the fight between Chris and Elbox. How and why did it start? Is it another one of those "I'm not getting paid per license" type of issues? If it is, I can't say I would stand behind Chris on it, I've been burned on that issue once. The best way to get an idea of how many posieden stacks are out there, put it in the program that requires registering the program itself through a web site or mail or email. Validate the s/n on the card with the list of cards gathered from the parent company (in this case Elbox), for each valid user, request a specified amount from Elbox. Why would a company want to make an assessment on something they know would cost them money. What should be done in the first place is to negotiate who will be making the assessment and who will cover those costs. As a software developer, you should know who your clientel is. If the parent company purchasing the B2B solution wasn't satisfied with previously mentioned steps, then the contract isn't worth it. The only other solution is to offer an up front fee with update costs. Say once a year you will provide software updates to fix potential bugs for a set amount. That amount could be negotiated each year depending on the requests for software updates.
In the programming industry you have to prepare yourself to be burned, otherwise you will get burned. Now I'm not sure if this is what actually happened, but from the hilights of the bickering, it looks likely.
:pint:
