The problem with external drives is that a lot of organizations do not want to have all their financial data simply hanging outside a machine on a portable drive. This is especially true for commercial entities. With all the fine work done on auditing and security in NV2 it seems counterproductive to recommend a huge security breach for confidential data.

For NV2 to be widely accepted QW will have to provide a better solution and a better explanation of hardware requirements for both client and server. Without the source code everyone is left to their own peace meal way of trying to solve this problem. In my humble opinion this has all the signs of threading problems and not USB vs. SATA vs. SCSI. vs. ATM.

One NV2 consultant I spoke with, who was very helpful, said they have solved the problem but he would not disclose how because they spent so much time and money finding the solution. He recommended buying one of his servers for approx. $7000 US. Unfortunately my client does not want to buy a machine except from a local source where they can receive prompt service. Another consultant said to run NV2 Server on a completely separate workstation and not use Windows Server software but rather Windows 2000. What does QW suggest?

A few days ago I called QW support because NVEXPORT was hanging and I was told to set the properties of the NV1 shortcut to full screen, set the idle sensitivity to lowest, and place some object on the key during the export. This was a great solution since it cut my export time by 1/3 and removed the hanging problem. This needs to be included in the documentation for NVEXPORT so that others don’t have to waste so much time finding it for themselves and reduce the calls to QW support.

Sharing solutions is in everyones interest. The more NV2 is adopted the more NV2 consultants will have opportunities to gain new clients and of course the more QW will make through sales. I would imagine that many consultants are quite gun shy about recommending NV2 to new multi-user clients until they have solved the performance problems.