Tamar,
as Kathy already said she installed the 32bit version all that won't matter much for her, also I don't have Office2013, only 2010.
But as it's new to you, indeed I have the 64bit Office installed, starting eg Excel 2010 an info screen shows it's 64bit. I can still automate it. That's not very surprising, the OLE classes are embedded in an EXE, therefore Excel.Application starts a new process, it's an out-of-process COM server (EXE), not an in-process COM Server (DLL), and you can start any EXE from VFP, no matter it 32bit or 64bit.
I have these folders
C:\Program Files\Microsoft Office\Office14 -> Main install with all the application EXEs, 64bit.
C:\Program Files (x86)\Microsoft Office\Office12 -> mainly one file: STSLIST.DLL, also STSLISTI.DLL and CHM (The CHM shows it's about Access Web Datasheet)
C:\Program Files (x86)\Microsoft Office\Office14 -> more DLLs, but no EXE.
I think the x86 folders contain only some 32bit help DLLs, or are from the readonly viewers I had installed earlier.
The problem with 64bit is inverse, Office 64bit can't see and use 32bit ODBC drivers or OLEDB providers. But that's not a problem for me.
There still is no very good reason to install Office as 64 bit application. You don't gain much, the technet link above tells us Excel files are allowed to grow over 2GB, but that won't help you in conjunction with VFP. Word processing also does not get more stable with 2GB or larger docx files.
Bye, Olaf.