I installed Excel 2010 Beta 64. I registered the J64-602 EXE and DLL.
The Excel VBA J code now reports that it is using J64:
Got J64
--
David Mitchell
On 1/24/2010 7:48, David Mitchell wrote:
> I was not able to uninstall J32 using the instructions in the current J602
> doc:
>
> Windows
> Delete the J program group by clicking Start|All Programs then right clicking
> the J program group and selecting delete.
>
> If you registered J as a COM server you can unregister it by running
>
> ....> [path to J install folder]\j.exe /unregserver
>
> Running J with the unregserver option gave the error: Unregister not
> supported.
> Using the unregister option resulted in the same error.
>
> Running regsvr32 /u j.dll from the j32 bin directory said that
> DllUnregisterServer in j.dll succeeded, but J32 j.dll was not removed from the
> registry. The following 3 keys were present both before and after all
> attempts
> to remove j32.
>
> HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{21EB05EA-1AB3-11CF-A2AC-8FF70874C460}
> HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{21EB05EA-1AB3-11CF-A2AC-8FF70874C460}
> HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{21EB05EA-1AB3-11CF-A2AC-8FF70874C460}
>
> If I manually rename j.dll in the j32 bin directory and rerun the test VBA
> program, Excel reports that the specified module cannot be found.
>
> Some doc from Microsoft (http://support.microsoft.com/kb/896459) says:
>
> 32-bit programs run in WOW64 mode and access keys and values that are stored
> in
> the following registry sub key:
> HKEY_LOCAL_MACHINE\Software\WOW6432node
>
> and
>
> To support the coexistence of 32-bit and 64-bit COM registration and program
> states, the WOW64 subsystem presents 32-bit programs by using another view of
> the registry. The WOW64 subsystem uses registry redirection to intercept
> registry calls at the bit level. Registry redirection also makes sure that the
> registry calls are directed to the correct branches in the registry.
>
> So it appears that uses of DLLS from 32 bit apps on a 64 bit system will be
> redirected to have access to only the 32 bit DLLS.
>
> I'll take a look at Office 2010 later.
> --
> David Mitchell
>
> On 1/23/2010 20:44, bill lam wrote:
>> I suspect that the ole object was called by a specifying its progid
>> which is the same for both 32 and 64-bit versions. The ole
>> infra-structure choose from available candidates that have the same
>> progid for you. In this case the 64-bit dll was rejected and it can
>> only elect the 32-bit dll. If you remove the J32 installation, I
>> guess it will just fail this test.
>>
>> It seems there is an office 2010 64-bit beta available for download
>> from m$ site, perhaps you may try that as well.
>>
>>
>> sab, 23 Jan 2010, David Mitchell skribis:
>>> Here is an example of calling J from Excel 2007 on a 64 bit OS.
>>>
>>> http://www.jsoftware.com/jwiki/Scripts/JfromExcel
>>> --
>>> David Mitchell
>>>
>>> On 1/10/2010 22:23, bill lam wrote:
>>> [---=| TOFU protection by t-prot: 21 lines snipped |=---]
>>
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
