Hi Daniel,

An Access Violation error message is quite generic, sort of like the Windows message 'This program has performed an illegal operation'. Basically, the system has tried to execute a function and at that instant of time some something was supposed to happen, it couldn't. There are potentially numerous causes of this error message and sometimes quite difficult to track down.

Were you trying to print reports or forms in Adagio Order Entry? This makes a difference as these use separate printing routines.

That things were working normally after closing and re-opening the program, I would think that the condition which caused the error went away - but certainly wouldn't guarantee that the error won't return. The first places I would look at are available memory on each workstation (including how many other programs are running at the same time) and the network hardware, including cards and hubs. The faster the better, especially for transfer of multiple data files like Adagio and other accounting packages do.

Also make sure that in a multi-user environment, all program and data files are sharable on the network, and any settings such as Opportunistic Locking are disabled.

Regards,

Hi Daniel,

Thanks for the update and information.

After some searching, we found that the address you included with the Access Violation message is consistant with the function that loads the list of specifications you can select to print from. When someone chooses to print a spec (invoice, check or whatever), Adagio looks for all the appropriate specification files it can and builds a list. When the Print Dialog opens, you have the option of selecting any spec from that list.

Are you aware if anyone else was attempting to print a specification at the same time when the error was produced? R&D thought there might be a chance that a timing issue occured when two people tried to print and build that list at the same time. It's a hard thing to test and duplicate.

One thing you can try is to reduce the number of specifications in your data directory, to decrease the amount of time it takes to build that list. For example, Adagio creates a number of sample specifications for you, and you could remove those you don't use. All Adagio OE specs have file names that start with OE$.

It sounds like you've taken the right steps in all the other areas (hardware, disabling NAV auto-protect, etc).

If it matters, there is a new PTF for Order Entry that is now available for download. There was nothing fixed that would specifically address what you have run into.

Regards,

Here's the URL, which can also be accessed from the End Users section and the link to PTFs.

Adagio OE PTF

Please note that I'm not promising this PTF will address the specific error you are running into.

Regards,