Am I allowed to say "female dog"ing about Office 2013?

[ChrisGreaves]

http://www.chrisgreaves.com//Greaves/Admin/Domains/Technical/200322013/index.htm
OK.
My reputation as a complainer remains unblemished.
I am documenting my efforts to overcome the "Compatibility" error reported by Rudi (Post=128262 ) in Advice on cleaning up a Word document

There are some aspects of MSoft that still baffle me. I'll be updating the web page over the next week or so.

[HansV]

Chris, I see that you installed 64-bit Office "because I am running a 64-bit version of Win7 on a 64-bit computer". I'm sorry, but that is not a good reason for installing 64-bit Office. Microsoft explicitly recommends 32-bit Office (even on 64-bit Windows) for most users. The 64-bit version is only necessary if you need to work with very large Excel workbooks, or to open a very large number of workbooks simultaneously. But 64-bit Office has serious compatibility issues.

See Choose the 32-bit or 64-bit version of Office:

In most cases, install the 32-bit version of Microsoft Office. We recommend the 32-bit version of Office, because it helps prevent compatibility issues with most other applications, especially third-party add-ins.

Office installs the 32-bit version automatically even if your computer is running 64-bit editions of Windows. You might want to install the 64-bit version of Office if you usually work with extra-large databases or worksheets or develop for the 64-bit platform.

[Rudi]

Also see this lounge thread...

[ChrisGreaves]

Chris, I see that you installed 64-bit Office "because I am running a 64-bit version of Win7 on a 64-bit computer".

Mea Culpa.
I guess I'm still burned from my migration WinXP-->Win7 about four years ago when all-of-a-sudden (to me) Many of my working Windows aps ceased to run.

That said: "Office installs the 32-bit version automatically even if your computer is running 64-bit editions of Windows. "
I confess to being puzzled.
I am sure I have downloaded the 64-bit package (see once-bitten-twice-shy not above) so it now sounds to me as if MS was should be clever enough to install the 32-bit Office.

In which case I puzzle over the MS edict that I had to remove my 32-bit version of Office 2003 before I could go ahead and install.

I wanted both versions running so that I could upgrade my VBA code (to PtrSafe specifications) and then re-test it in the old 2003.

I'll see if I can't d/l the 32-bit version of Office 2013, delete my current installation, reinstall my 32-bit Office 2003 and then try to install the 32-bit Office 2013 on top of that.

But
(a) this all seems like an awful lot of work just to resolve conflicts in the MS way of doing things and
(b) I suspect that the two users who have reported compatibility problems to me might be running 64-bit Office2013, since the PtrSafe option seems to be tied up with "long LONG" integers.

(signed) "Not loving it" of Toronto

[ChrisGreaves]

Also see this lounge thread...

Thanks Rudi; please see also my reply to HANS.
Out of interest: when you got the compatibility issue were you running 32- or 64-bit Office 2013?

[Rudi]

32 bit

[BobH]

This thread got me to wondering which version I have installed. It took a bit of looking around (because the ribbon doesn't include a Help menu) but I found under File > Help a statement at the right of the screen telling me that I have the 32-bit version installed.

Even blind squirrels find nuts, occasionally.

[Rudi]

So now you can update your footer to:
Intel Core i5 3570K 3.40 GHz, 16 GB RAM, ECS Z77 H2-A3 Mobo Windows 7 HP 64-bit, Office 2010 (32-bit)

[BobH]

So now you can update your footer to:
Intel Core i5 3570K 3.40 GHz, 16 GB RAM, ECS Z77 H2-A3 Mobo Windows 7 HP 64-bit, Office 2010 (32-bit)

Yes, Yoda! Fixed it, I did.

[Rudi]

Mighty fine to, does it look.