I like the idea of automating invoice numbering; but I have another application for the same idea - creating membership numbers for sign-up pages.
However, I have my own slant on this and I wonder if anyone has any thoughts on whether it would work before I go ahead and make a fool of myself.
The idea is to have two or three separate membership sign-on pages, for basic, intermediate and agent members. Each will have its own modified checkout.pl cgi, but all will refer to a single member.dat file for the incrementing serial number. This way I can automatically give everyone a single unique sequential membership number but deal with them through separate database entries (modified e-mail responses and database scripts for different information on applications forms, etc.).
Obviously with three checkout.pl scripts using a single *.dat file there is every chance of a conflict. Is this likely to occur or would my web server, and the scripts, be able to handle the load and any conflicts?
- Escrow merchant accounts. Creating A World Of Trust.
"/" Stroke, what you do to make a woman happy.
"\" Backstroke, what you do to a woman after you've made her happy.