You are right. It does not make sense from the QlikView point of view. To be precise, the Plugin, like the Desktop is the client software that the users have to view and interact with a QlikView document.
But that does not mean that, if you are running a 64 bit Server and a 32 bit laptop you are unable to open the documents. However, it's true as well that you need to have the same version and release (for example, version 11 SR1 release 11282) of Plugin, Desktop and Server.
Furthermore and for what it's worth, and this might have lead to confussion, pasted from the Release Notes:
QlikView 11 is the last release of QlikView Server and QlikView Publisher that will support 32-bit operating systems.
In regards to the Internal Inconsistency Error Type A-D they are very generic error messages that unfortunately cannot be addressed without knowing a lot about the environment where QlikView software is running but yes, it may happen because lack of memory because of the size of the file, among some other reasons.
Hope that helps.
Just to add to Miguel's response, you can quite happily mix 32bit and 64bit in the same environment. Lots of customers do it. QVWs don't really care which platform they run on.
There is one complication I have come across, and that comes from the "CONNECT" statements within QlikView scripts. The default, just plain "CONNECT" will use the OLE or ODBC datasource as the same number of bits as the host operating system, so for example on a 32bit system it will use a 32bit driver. The complication is when a 32bit developer uploads a document to a 64bit server and you only have a 32bit driver. It will fail. The answer in that scenario is to use "CONNECT32" instead which will force it to use a 32bit driver.
Aside from this one issue mixing it should be fine.
I have installed 64bit QV Personal Ed, 64bit Windows 7 and 32bit Ms Office. When I open Script Editor and loads Ms Access file thru ODBC Connect and select MS Access Database it gives an error
Error: SQL##f - SqlState: IM014, ErrorCode: 0, ErrorMsg: [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application"
Is there any solution without cahnging Ms office to 64bit version? Becase I have an excel add-in that works only on 32-bit version. So I dont want to lose that add-in also.
Also I have designed a QV app on 64bit QV version, if I moved to 32bit QV, would it work on it?
Thanks and regards