I spent quite a bit of time today doing testing on this problem.
First off, I copied the data to the local "C" drive as Steve suggested and posted there. It posted the batch with two invoices totalling over 700 items in 15 seconds flat, versus 28 minutes on the Novell server. A testament to your code Andrew. I turned on the option you suggested Andrew, and I could see the reads and writes happening as you described. Suspecting a network or Novell problem, I copied the data to the Windows Terminal server, where it took almost 35 minutes to post! My next step was to connect the workstation and both servers to a new gigabit ethernet switch, with nothing else connected. The test post was repeated. It made no difference. It still took about 28 minutes on the Novell server and 35 minutes on the Terminal server. I then installed the Adagio software on the Terminal server, connected via remote desktop and posted. The data posted in less than 15 seconds, the same as with the local copy on the workstation. It appears when the number of line items in a batch gets large that the network becomes an issue. I am wondering if keeping the data and programs on the Terminal Server would be a bad idea in this case. There is seldom more the three or four users working at one time, and mostly they are are on different data sets at the same time. The Terminal server notes say this is not a recommended or supported method.
Do you have any other suggestions? They do not appear to have posting issues untill the large line item invoices are posted. Thanks for your assistance!