That the errors had previously gone away after rebooting, even though it's not presently the case, leads me to suspect that the problem is related to the network or computer environment, rather than a program error. About how long have these errors been happening? Since Day 1 or at some point since then?

Here are a few questions/hints that hopefully will narrow down the search for the solution.

- When the errors started happening, what changed? This could involve a number of different things, such as (but not limited to) installing new software, upgrading the computer or the network, putting on new Client software, setting up your anti-virus software to run in Auto-Protect mode, changing your Windows login settings, not having full rights to the data/program directories and/or files, etc.
- Does the same error occur if you attempt to run the program from a different computer?
- Does the error occur because another user is also using the program?
- If you reinstall Adagio Invoices, does the problem persist?
- If Adagio Invoices is installed on the network, try installing it on a local C drive, make a copy of your data and also put in on your local drive, and try to run it here. This would point out the network should this run successfully.
- The version of Adagio Invoices you have (6.5A) is a couple of years old, and is a 16-bit Windows application. The current release (6.8A) has been upgraded to a 32-bit Windows application. This could make a difference if you are running Windows NT/2000/XP.
- If you are running one of the above Windows versions, make sure that Opportunistic Locking is disabled on all computers.

Unfortuneately, problems such as these often requires some detective-work and some guessing as well. You might want to try the 'simplest' scenario (using a locally installed Adagio Invoices with a local copy of the data, logged into Windows as Admin) and see if that works. If so, add a new variable (such as trying to access the live data on the network, everything else being the same) and determine the results. Eventually, you will probably hit the cause of what's preventing you from running the program.

Regards,