Stuart McLachlan
stuart at lexacorp.com.pg
Fri Jul 3 15:29:40 CDT 2009
That's not an uncommon requirement. I've got one Club Memerbship system which does that automatically. The first x membership numbers are reserved for life members. When a membership lapses, that numbe becomes available again. When a new member joins, the are assigned the first available ordinary membership number. Life membership numbers are not re-used If someone is elected as a new Life Member, they are given the next sequential Life number - there are enough in the pool to last form many, many more years. Of course, I don't use the membership number as the PK :-) -- Stuart On 3 Jul 2009 at 9:45, Susan Harkins wrote: > They said "One stipulation the new > > program has to maintain the look and feel of the original worksheet". > > =====My war story: A client using an old db program needed (really, wanted) > sequential id numbers. To accomplish that, he'd been reusing pk values for > years -- when he would delete a record, he would write down the number and > then enter that number for the next record's id value -- totally insane. > > He was furious when my Access interface didn't allow him to reuse numbers. I > kept explaining that it was totally unnecessary. He just didn't get it, and > we never finished the project. Now, I had accommodated him in that each > record displayed a sequential id number automatically -- but that wasn't > good enough, he wanted control, he wanted the ability to enter deleted id > values himself. I refused. He fired me. In retrospect, I should've given him > what he wanted, allowed him to go through the process... it wouldn't have > mattered, I was already using an AutoNumber pk that he couldn't see, so > wouldn't have meant balls... he was insane and I just didn't think fast > enough on my feet. > > Susan H. > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com