When deleting a job in PJC for which no entries have been posted the code looks through AROBLJ and APOBLJ for open balances on job related detail lines. There's no index on Contract, Project, Category on these tables so the process is reading all rows in the table, over and over again. On a 3 user, 3 GB SQL Server database deleting a job took over 20 minutes.

Added Feb. 20, 2015

Comments

  • Hi Sage, agree. Add and use ore indexes across all of PJC. Its the least you can do for this product, which has been left languishing without any dev for many years.

    Also - Sage - please add the votes from the same idea "Deleting jobs in job costing is sloooooooooooooooooooooooow"