Date: Tue, 29 Sep 2009 02:36:36 -0700
Reply-To: Alex <alexander.konn@IEA-DPC.DE>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Alex <alexander.konn@IEA-DPC.DE>
Subject: Re: SAS from spreadsheet
Content-Type: text/plain; charset=ISO-8859-1
On Sep 25, 7:41 pm, mcqu...@dasconsultants.com (Gary McQuown) wrote:
> I don't do CT, but we have done this, it is very doable and there is at least one book on the topic. Look under "automation" and/or "data driven processing".
> 1) Use access not excel and use forms for entry. This avoids many issues.
> 2) Use SQL server for the back end. Same reason.
> 3) The access values are just SAS macro parms, including the name of the macro to call.
> 4) Create a history table to log tasks assigned, started, completed and to capture error codes. Then have a deamon call the tasks.
> Gary McQuown
> Data and Analytic Solutions, Inc. (DAS)
> 3057 Nutley Street, #602
> Fairfax, VA 22031
> Tel: 703-628-5681 Fax: 703-991-8182http://www.dasconsultants.com
Could you provide the name or any further information about the book
you mentioned? Does it focus on SAS? I couldn't find it on Google and
We aren't doing CT, either. But I am thinking about providing our QA
people with a tool that helps them test our SAS applications. Right
now this involves a lot of manual work on their side plus they are not
very proficient in SAS. So I want to enable them to create their test
cases in standardized spreadsheets and run them with a tool which
performs some standard assertions and creates an output displaying
success/failure for every test case. Until now I wanted to do this
with Excel, because this seemed to be the easiest way for everyone
involved. But probably you are right and one should rather use an SQL
DB with a GUI front-end.