8
Apparently I had not made it clear originally. The member number field in my 2.2.4 installation has already been created. Each time somebody joins the organization we register them on out site. The XOOPS database serves as our membership database. If a new member has already registered on the site we edit their record to include such things as their member number, join date, expiration date, etc. A couple of different people are involved in administering this aspect.
At present the database field for member number does not have to be unique so that it is possible to enter duplicate numbers for two different people. To avoid that we have to keep track of the numbers or look up what the last number used was. It would be nice if XOOPS would not allow the people doing this work to accidentally enter a duplicate.
I thought of make the field unique directly in the database and tried it, via phpmyAdmin, but it did not work for some reason. I'll have to try it again. Any advice on how to do that?
I also don't know what the behavior will be if I do succeed in doing that. Will I get a standard XOOPS message if a duplicate is entered?
Barry
Barry Cooper
Sweet Home, Oregon