[18983] in s-news-athena
[S] winNT workgroup design?
daemon@ATHENA.MIT.EDU (Dave Cacela)
Thu Aug 19 17:34:14 1999
Message-Id: <61A76FCF917ED211B56500A0C9E3D7B81D6C94@GUARDIAN>
From: Dave Cacela <DCacela@stratusconsulting.com>
To: "'s-news@wubios.wustl.edu'" <s-news@wubios.wustl.edu>
Date: Thu, 19 Aug 1999 15:32:44 -0600
Mime-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
S-folk:
I have questions about developing a system for several splus users to
cooperate over a winNT network. User cooperation for my group in general is
fairly primitive at present but there's a willingness to experiment with
standardizing on splus. Our objectives include reducing the frequency of
data transit between software formats (e.g., splus/excel/access/etc) and
standardizing graphics styles and data reporting.
Given the variable needs and skill sets of users in my group, which includes
non-programmers and non-statisticians, I think I can avoid the $$ expense of
puchasing additional splus-pro licences by opting for "splus standard"
instead (a cheaper version with no command line). However, I have no
experience with splus standard and I don't know if/how well it works in a
network.
I've sent these Q's (detailed below) to Mathsoft and await a reply.
Meanwhile, I welcome input from readers of this list who would describe
their experiences and/or suggestions.
Thanks
--dc
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dave Cacela 303-381-8000 x247 (voice)
Stratus Consulting 303-381-8200 (fax)
Boulder, Colorado
dcacela@stratusconsulting.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~
Our current setup is:
> NT network installation of splus pro 2000 with license for 1 user
> No single-machine installations.
I'd like to have more people in our group using splus, but they will be
generally more casual users, i.e., not oriented towards programming.
Therefore, I don't think that they would make use of the command line access
that splus pro offers.
Ideally, all user(s) would be able to share project directories through our
NT network, but only one of us (me) would ever need to use a command line.
Secondary users would mainly be:
> sharing data frames produced by other users
> producing graphics or simple stats calcs using the gui or by running
scripts.
> using gui to produce graphics and then grabbing parts of history log for
conversion to scripts
I don't really care about distinctions between network licensed installation
versus single machine licenses as long as users can share data effectively
and I'm not wasting money to buy capacities that won't be used.
So my questions are:
How can we get to where we want to be without purchasing additional licenses
for full-blown splus-pro?
What are the limitations in splus standard regarding:
>network integration with splus pro
>writing and executing scripts
>does it have the same scripting and history logging that I'm accustomed to
with splus pro?
> what are the important distinctions between splus standard and Axum? How
well would Axum integrate with splus pro instead of splus standard?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----------------------------------------------------------------------
This message was distributed by s-news@wubios.wustl.edu. To unsubscribe
send e-mail to s-news-request@wubios.wustl.edu with the BODY of the
message: unsubscribe s-news
