I put in a request to our IT department to upgrade my computer to a 64 bit operating system because I work with large files and I often have memory issues that cause my QV10 SR5 to crash or more commonly give me an Internal Inconsitency Type D error, which prevents me from saving the document I was working on and I have to ditch an hour's worth of work and start over. I know save often is a bit of a cure for that problem, but I think it would be much more efficient to have more memory (I'm maxxed out at 4gb for my 32 bit windows 7 OS).
My IT department responded that they couldn't update me because they would have to upgrade all my user's plugins to 64 bit versions if they changed my QV to a 64 bit version. That doesn't sound right to me. Why would the plugins be required to be 64 bit to open a document saved by a 64 bit machine? If I buy a 64 bit version of MS Excel, I can send anyone a file that was created using that software and it will have no problem functioning on a 32 bit machine unless it was just too big for the 32 bit machine to handle it. Our server is 64 bit and it has a pretty decent amount of memory (at least 16gb), so I think the 32 bit plugins should be able to run the documents just fine because they don't store the documents in their memory.
Am I wrong about this?
PS - I've searched for common causes of the internal inconsistency type D error and found most to point to bad scripting or not enough memory. If using loops in scripts to load multiple excel spreadsheets causes the problem, I would appreciate a heads up on that as well. My IT person says that this would cause the problems I'm having, but I don't agree with that either. The poor woman is at her wits end with me and has told me to seek help elsewhere. I don't get the error when I am reloading. I get the error when I alter or create a pivot table that becomes overly large due to a lack of selections to narrow the scope of the report. Unfortunately, my users tend to use QV as a data warehouse and they tend to want extremely large chunks of output, so I can't really limit these pivot tables to a given number of items etcetera.