Re: [Rcom-l] Passing a COM object pointer does not work in the new rcom package

2008-10-29 Thread Thomas Baier
Dear Vilmos, thanks for your mails and the very good analyses of the problem(s). I've prepared a version of rscproxy including fixes for both problems. The new version of rscproxy should be available from CRAN soon. The following code (slightly changed your code) now works: XL<-comGetObjec

RE: [Rcom-l] Problem installing RSrv250.exe

2008-10-29 Thread Hanák Gábor
Sorry, Greg, It is reporting the same problem. What I did was: 1. I completely removed R 2.8.0 2. I completely removed R/Scilab (D)Com Server 2.50 and RExcel 1.75 3. I installed R 2.7.2 (it was fine) 4. I installed R/Scilab (D)Com Server 2.50 and RExcel 1.75 Unfortunately upon completion of task 4

RE: [Rcom-l] Problem installing RSrv250.exe

2008-10-29 Thread Greg James
Gabor, RDCom is not currently compatible with R-2.8.0. I had the same problem and found that R-2.8.0 no longer installs an rproxy.dll file which is what RDCom is programmed to look for. There is no workaround right now except dropping back to R-2.7.2 which is what I've done. The VBA error message

[Rcom-l] Problem installing RSrv250.exe

2008-10-29 Thread Hanák Gábor
Can anybody help me with the following installation probelm? I use Windows XP Professional Version 5.1 (SP3) I use Microsoft Office Excel 2003 SP3 I successfully installed R 2.8.0 When I wanted to install RSrv250 it went smothly for a while and after I got a message saying "Completing the R/Scilab

[Rcom-l] stack inbalance when getting date value

2008-10-29 Thread Prokaj Vilmos
Dear Thomas, In the following lines of code the activecell contains a date/time value XL<-comGetObject("excel.application") a<-XL[["activecell"]] a[["value"]] Warning: stack imbalance in '.Call', 16 then 17 Warning: stack imbalance in '{', 14 then 15 Warning: stack imbalance in '[[', 2 then 3 [1

[Rcom-l] Passing a COM object pointer does not work in the new rcom package

2008-10-29 Thread Prokaj Vilmos
Dear Thomas, I think I finally catched the bug. In the bdx_com.c file in the BDXScalar2Variant function the BDX_HANDLE case was handled in the following way: case BDX_HANDLE: { LPSTREAM lStream = pBDXData->data.raw_data[0].ptr; void* lTmpPtr = (void*) V_DISPATCH(pVariantD