TOM_T
Browser

I love YaBB 1G - SP1!
Posts: 4
|
THE MORE I THINK ABOUT THIS, THE POTENTIAL FOR LOCKING ERRORS IS ENORMOUS. JUST TO BEGIN WITH, AS YOU START AN ORDER, THE FIRST CHANCE OCCURS WHEN YOU HAVE TO CHOOSE A CUSTOMER. UNTIL THAT CHOICE IS MADE, THE PROGRAM IS LOOKING AT THE ABSENSE OF A CHOICE AS THE SAME CHOICE AMONGST THE USERS AND LOCKS. YES? MORE THAN ONE SALES ORDER FOR THE SAME CUSTOMER BEING ENTERED SIMUTANEOUSLY SHOULD NOT CREATE A PROBLEM UNLESS THE PROGRAM IS REGISTERING THE "CHOICES" AS THEY OCCUR BY SAVING THEM INDIVIDUALLY. COULD THIS BE EASILY CHANGED TO OCCUR WHEN DOING THE FINAL SAVE AT THE END OF A SALES ORDER, P.O., OR WHATEVER? MAYBE AS WE MOVE FROM PARENT TO CHILD RECORDS AS IN SALES ORDERS [THAT'S WHEN THE NUMBER IS ASSIGNED], BUT INSTEAD OF LOCKING UP, THE "SAVES" ARE PUT IN A TYPE OF QUE AND PROCESSED IN THE ORDER THEY ARE REQUESTED. YOU DON'T LOOSE THE WORK YOU'VE DONE, BUT MAYBE ONLY 5 SECONDS OR SO WHILE THE REQUEST IS BEING PROCESSED AS OPPOSED TO BEING DENIED ACCESS. ANY THOUGHTS ON THIS?
|