Gustav Brock
gustav at cactus.dk
Thu May 8 07:55:00 CDT 2003
Hi Ervin Before you'll get beaten by the normalization gurus of the list (I'm one but I don't beat) you should consider to split those sort orders out to separate (numeric) fields. In the long run I'm convinced it'll save you a lot of trouble. /gustav >> Why not simply update the SchoolOrder: > I think you were right that sometimes I have to update the field > SchoolOrder. If I use John's system(and I think I will) where the > SchoolOrder consist from 2 parts: "Group.OrderInGroup" everything is ok, > except when arise a new group which have to shift the existing groups or > orders... > I have to admit that part "Group" here means City, the part "OrderInGroup" > is order within a group(within a city) and the field SchoolOrder is here to > sort schools in order how will salesperson visit them. > E.g. when new first group arise then each Group have to be incremented. The > same is for the part OrderInGroup: e.g. when arise new first in some group > then the part OrderInGroup have to be incremented... > Thanks anyway, I'll try to make some update queries tomorrow.