Is Locking necessary in Reservation Entry Table??

baigs_arshi2004

Kindly let me know whether Record Level Locking is necessary for Reservation Entry table?? Because when ever a user enters quantity in Sales Order/Invoice or Transfer Order, it locks the Reservation Entry Table and other user is not able to enter the Quantity. Is there any harm if I comment the code which Locks the Reservation Entry Table ..... Kindly advise....

Alex_Chow

What version are you using?

You can try taking the lock out for a few days and see what happens. Locking is used so no other person can modify the same record.

kriki

If you are working on a Navision DB, it will change not a lot because inserting/modifying anorder line blocks the whole table. You COULD only gain something if users are working on different tables.
If you are working on SQL, the locktable locks only records that are read AFTER the LOCKTABLE-command, so also there is not much to gain.
The best you can do is tune your code and indexes/SIFTS (for SQL) to do the inserts/modifies as fast as possible and start writing to the DB as late as possible.
If you are working on a Navision DB, best use the COMMIT-cache if not in use.

Marije_Brummel

In 3.7 there reservations is a nag when not used.

You can just take out all references and it will run much better.

Also apply build 19868 because of the message window locking issues.

Good luck.