From c59264b027f8e4294991acb34998d1b596dccf3f Mon Sep 17 00:00:00 2001 From: Kathy Date: Mon, 28 Oct 2013 13:55:47 +0000 Subject: [PATCH] Bad character in column number for FNP data --- PROMS/VEPROMS.CSLA.Library/Config/ProcConfig.cs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/PROMS/VEPROMS.CSLA.Library/Config/ProcConfig.cs b/PROMS/VEPROMS.CSLA.Library/Config/ProcConfig.cs index dca13627..edae8c26 100644 --- a/PROMS/VEPROMS.CSLA.Library/Config/ProcConfig.cs +++ b/PROMS/VEPROMS.CSLA.Library/Config/ProcConfig.cs @@ -235,7 +235,7 @@ namespace VEPROMS.CSLA.Library if (s == string.Empty) s = _Xp.ParentValue("Format", "Columns"); // get the parent value // If there is no parent value, then use the volian default - if (s == string.Empty) + if (s == string.Empty || s == "t") // fnp aop1 had this (not sure about other fnp data) return FormatColumns.TwoColumn;// At the procedure level, default to Two column return (FormatColumns)int.Parse(s);