I figured this one out. My TOP_COLUMN was typed as NOTE. I hadn't even considered that. It's value is a Fiscal CCYY, returned as TEXT via a CALL to a Stored Procedure. However, when I use this in a view, then save the view to create a 'base' table, it appears to be implicitly typed as NOTE. (I'm pretty sure that my original PUT of the Stored Procedure explicitly typed the Return Value - thanks to whomever on the list pointed that out to me a week or so back.)
Anyway, I'd like to ask Razzak and RBTI if would be possible for CROSSTAB to check for invalid data types, then, if found, throw an error message, rather than throw out the program. This ain't no complaint, just polite request. Admittedly, the root-node cause (how do you like that phrasing, Jim [Bentley]) is mine, but I think it would be far more elegant to tell me I screwed up rather than just punish me without my knowing why. My Ever-Decreasing-In-Value $0.02 (Should I convert to Euro's, ozs of gold, bbl light-sweet crude?), Steve in Memphis -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Wills, Steve Sent: Thursday, March 13, 2008 11:26 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RBv8, Vista, CROSSTAB Abort ... Any ideas on why I could be having aborts from RBase when I execute a CROSSTAB at the R>? I had a problem with this once and thought it was because I was running it against a reasonably complex VIEW. This is against a table with only 400-or-so rows. Thanks, Steve in Memphis J. Stephen Wills Program Manager, Research Informatics Office of the Vice Chancellor for Research University of Tennessee Health Science Center 62 S. Dunlap, Suite 400 Memphis, TN 38163 Office: 901-448-2389 FAX : 901-448-7133
