Re: [Rcom-l] status RExcel, rcom, rscproxy, R2.8.0: confused still

2008-10-31 Thread Murray Eisenberg
That was an older post. I've gotten the (D)COM beta and RExcel to work with R 2.8.0 by explicitly setting the path to (D)COM in RExcel. Thomas Baier wrote: Murray, Murray Eisenberg schrieb: Still, when I I try "Server 01- Basic Test," I get a pop-up "StatConnector Test" window. If I click th

Re: [Rcom-l] status RExcel, rcom, rscproxy, R2.8.0: confused still

2008-10-31 Thread Thomas Baier
Murray, Murray Eisenberg schrieb: Still, when I I try "Server 01- Basic Test," I get a pop-up "StatConnector Test" window. If I click the Start R button, I see: Loading StatConnector Server... Done Initializing R...Function call failed Code: -2147221485 Text: installation problem

Re: [Rcom-l] status RExcel, rcom, rscproxy, R2.8.0: confused still

2008-10-31 Thread Murray Eisenberg
First, I don't know what it means to say that a server is typed or untyped. Second, I never put any programs on C: unless their installers give me no choice. Drive C: is for the operating system, device drivers, etc. I reserve drive D: for programs. Such granularity makes backing up easier a

Re: [Rcom-l] status RExcel, rcom, rscproxy, R2.8.0: confused still

2008-10-31 Thread Erich Neuwirth
Did you do an uninstall of the previous version of the (D)COM server? Your problem should not have happened if you had uninstalled. Were your servers configured as typed or as untyped? RExcelInstaller now installs RExcel in Program Files\RExcel One of the reasons is that it can even be used withou

Re: [Rcom-l] Update to R2.8.0: Can't copy Excel Worksheet

2008-10-31 Thread Christian Asseburg
I can confirm that now it works! Thank you! . . Christian On Thu, 30 Oct 2008 13:47:57 +0100, Erich Neuwirth <[EMAIL PROTECTED]> wrote: rscproxy 1.0-12 is out and will appear on your CRAN mirrors soon (Thanks Thomas!) Not Christian Asseburg's example works! library(rcom) E<-comCreateObjec

[Rcom-l] Re: Scilab trouble accessing library/macro

2008-10-31 Thread Bjorn
Please ignore the below question, I've found the problem and it had nothing to do with accessing library/macro. It was due to incorrectly named variable in the code. Bjorn 2008/10/30 Bjorn <[EMAIL PROTECTED]> > Hello, > > I'm using the DCOM server with Scilab 4.1.2 and calling the functions from