TPT script load an other file when running - teradata

I have an issue with my script when i use it outside of TPT Wizard. So basically it load an other file than the file i want to load. Here is the error and the code. I want to load the .txt file and not the one the windows prompt command loads. It's very stange because the script point to a txt file and not the csv file. Maybe I have to reset something with the Tbuild command like -d?
I could not find on the internet some information about it.
/* 1 */
/* 2 */
/* 3 */ DEFINE JOB txt2
/* 4 */ (
/* 5 */ DEFINE OPERATOR W_1_o_txt2
/* 6 */ TYPE LOAD
/* 7 */ SCHEMA *
/* 8 */ ATTRIBUTES
/* 9 */ (
/* 10 */ VARCHAR UserName,
/* 11 */ VARCHAR UserPassword,
/* 12 */ VARCHAR LogTable,
/* 13 */ VARCHAR TargetTable,
/* 14 */ INTEGER BufferSize,
/* 15 */ INTEGER ErrorLimit,
/* 16 */ INTEGER MaxSessions,
/* 17 */ INTEGER MinSessions,
/* 18 */ INTEGER TenacityHours,
/* 19 */ INTEGER TenacitySleep,
/* 20 */ VARCHAR AccountID,
/* 21 */ VARCHAR DateForm,
/* 22 */ VARCHAR ErrorTable1,
/* 23 */ VARCHAR ErrorTable2,
/* 24 */ VARCHAR NotifyExit,
/* 25 */ VARCHAR NotifyExitIsDLL,
/* 26 */ VARCHAR NotifyLevel,
/* 27 */ VARCHAR NotifyMethod,
/* 28 */ VARCHAR NotifyString,
/* 29 */ VARCHAR PauseAcq,
/* 30 */ VARCHAR PrivateLogName,
/* 31 */ VARCHAR TdpId,
/* 32 */ VARCHAR TraceLevel,
/* 33 */ VARCHAR WorkingDatabase
/* 34 */ );
/* 35 */
/* 36 */ DEFINE SCHEMA W_0_s_txt2
/* 37 */ (
/* 38 */ REGLE_OFS VARCHAR(50),
/* 39 */ OFS_FIELD_BC801 VARCHAR(50),
/* 40 */ ME131 VARCHAR(50),
/* 41 */ DATA_TYPE VARCHAR(50),
/* 42 */ DATA_TYPOLOGY VARCHAR(50),
/* 43 */ FU_REF VARCHAR(50),
/* 44 */ FU_FIELD VARCHAR(250),
/* 45 */ FU_FIELD_EN VARCHAR(250),
/* 46 */ CODE_RADAR VARCHAR(50),
/* 47 */ REGLE_RADAR VARCHAR(50),
/* 48 */ DEFINITION_RADAR VARCHAR(5000),
/* 49 */ MODIFICATION_REGLE_RADAR VARCHAR(50),
/* 50 */ ANACREDIT VARCHAR(50),
/* 51 */ ANACREDIT_CRITICAL_FLAG VARCHAR(50),
/* 52 */ NPE_FBE VARCHAR(50),
/* 53 */ CRE VARCHAR(50),
/* 54 */ IFRS9 VARCHAR(50),
/* 55 */ IFRS9_CRITICAL_FLAG VARCHAR(50),
/* 56 */ SHS_2018 VARCHAR(50),
/* 57 */ SHS_CRITICAL_FLAG VARCHAR(50),
/* 58 */ STRESS_TEST VARCHAR(50),
/* 59 */ STOP_1_BMRC VARCHAR(50),
/* 60 */ MANDATORY_OPTIMA VARCHAR(50),
/* 61 */ FRANCE_REPORTING_Data VARCHAR(50),
/* 62 */ DEFAULTING_RDI VARCHAR(50)
/* 63 */ );
/* 64 */
/* 65 */ DEFINE OPERATOR W_0_o_txt2
/* 66 */ TYPE DATACONNECTOR PRODUCER
/* 67 */ SCHEMA W_0_s_txt2
/* 68 */ ATTRIBUTES
/* 69 */ (
/* 70 */ VARCHAR FileName,
/* 71 */ VARCHAR Format,
/* 72 */ VARCHAR OpenMode,
/* 73 */ INTEGER BlockSize,
/* 74 */ INTEGER BufferSize,
/* 75 */ INTEGER RetentionPeriod,
/* 76 */ INTEGER RowsPerInstance,
/* 77 */ INTEGER SecondarySpace,
/* 78 */ INTEGER UnitCount,
/* 79 */ INTEGER VigilElapsedTime,
/* 80 */ INTEGER VigilWaitTime,
/* 81 */ INTEGER VolumeCount,
/* 82 */ VARCHAR AccessModuleName,
/* 83 */ VARCHAR AccessModuleInitStr,
/* 84 */ VARCHAR DirectoryPath,
/* 85 */ VARCHAR ExpirationDate,
/* 86 */ VARCHAR IndicatorMode,
/* 87 */ VARCHAR PrimarySpace,
/* 88 */ VARCHAR PrivateLogName,
/* 89 */ VARCHAR RecordFormat,
/* 90 */ VARCHAR RecordLength,
/* 91 */ VARCHAR SpaceUnit,
/* 92 */ VARCHAR TextDelimiter,
/* 93 */ VARCHAR VigilNoticeFileName,
/* 94 */ VARCHAR VigilStartTime,
/* 95 */ VARCHAR VigilStopTime,
/* 96 */ VARCHAR VolSerNumber,
/* 97 */ VARCHAR UnitType
/* 98 */ );
/* 99 */
/* 100 */ APPLY
/* 101 */ (
/* 102 */ 'INSERT INTO DB_FTG_SRS_DATALAB.DICOGLOB_VCOBALT (REGLE_OFS,OFS_FIELD_BC801,ME131,DATA_TYPE,DATA_TYPOLOGY,FU_REF,FU_FIELD,FU_FIELD_EN,CODE_RADAR,REGLE_RADAR,DEFINITION_RADAR,MODIFICATION_REGLE_RADAR,ANACREDIT,ANACREDIT_CRITICAL_FLAG,NPE_FBE,CRE,IFRS9,IFRS9_CRITICAL_FLAG,SHS_2018,SHS_CRITICAL_FLAG,STRESS_TEST,STOP_1_BMRC,MANDATORY_OPTIMA,FRANCE_REPORTING_Data,DEFAULTING_RDI) VALUES (:REGLE_OFS,:OFS_FIELD_BC801,:ME131,:DATA_TYPE,:DATA_TYPOLOGY,:FU_REF,:FU_FIELD,:FU_FIELD_EN,:CODE_RADAR,:REGLE_RADAR,:DEFINITION_RADAR,:MODIFICATION_REGLE_RADAR,:ANACREDIT,:ANACREDIT_CRITICAL_FLAG,:NPE_FBE,:CRE,:IFRS9,:IFRS9_CRITICAL_FLAG,:SHS_2018,:SHS_CRITICAL_FLAG,:STRESS_TEST,:STOP_1_BMRC,:MANDATORY_OPTIMA,:FRANCE_REPORTING_Data,:DEFAULTING_RDI);'
/* 103 */ )
/* 104 */ TO OPERATOR
/* 105 */ (
/* 106 */ W_1_o_txt2[1]
/* 107 */
/* 108 */ ATTRIBUTES
/* 109 */ (
/* 110 */ UserName = 'L291506',
/* 111 */ UserPassword = 'Pilote04!',
/* 112 */ LogTable = 'DB_FTG_SRS_DATALAB.DICOGLOB_VCOBALT_log',
/* 113 */ TargetTable = 'DB_FTG_SRS_DATALAB.DICOGLOB_VCOBALT',
/* 114 */ TdpId = 'FTGPRDTD'
/* 115 */ )
/* 116 */ )
/* 117 */ SELECT * FROM OPERATOR
/* 118 */ (
/* 119 */ W_0_o_txt2[1]
/* 120 */
/* 121 */ ATTRIBUTES
/* 122 */ (
/* 123 */ FileName = 'DICOGLOB_IMPORT_TERADATA.txt',
/* 124 */ Format = 'DELIMITED',
/* 125 */ OpenMode = 'Read',
/* 126 */ DirectoryPath = 'C:\Users\291506\Desktop',
/* 127 */ IndicatorMode = 'N',
/* 128 */ TextDelimiter = 'TAB'
/* 129 */ )
/* 130 */ );
/* 131 */ );

Looking at the image of the error output, it looks like it's trying to restart an earlier run. ("Found CheckPoint file: C:\Program Files...\291506LVCP. This is a restart job") You should be able to delete that checkpoint file and rerun.

Related

CSS property for IE8

What is the solution for rgba value and border radius value of 0.0 in IE8.
The error i get is
Value "rgba(250, 250, 250, .6)" is not supported. (8.0)
Property "-webkit-border-radius" is not supported. (8.0)
Option 1
http://jquery.malsup.com/corner/
Option 2
http://code.google.com/p/curved-corner/downloads/detail?name=border-radius-demo.zip
Option 3
http://css3pie.com/
Option 4
http://www.netzgesta.de/corner/
Option 5
See this question
EDIT: Option 6
https://code.google.com/p/jquerycurvycorners/ - border-radius.
For rgba you can try create .png image with opacity and sat him as background
or try
.transparent_class {
/* IE 8 */
-ms-filter: "progid:DXImageTransform.Microsoft.Alpha(Opacity=50)";
/* IE 5-7 */
filter: alpha(opacity=50);
/* Netscape */
-moz-opacity: 0.5;
/* Safari 1.x */
-khtml-opacity: 0.5;
/* Good browsers */
opacity: 0.5;
}

CSS Active Class won't be respected in browser?

I'm trying to make a navigation of buttons. When one button is clicked, that anchor tag changes its background color to show that it is active. I'm using the background property with gradients but when I apply the active class to a link, the background doesn't change colors. I've tried looking in the Chrome Console and it simply shows that the new background color is loaded but it does not apply it. (It has the line through it as if it is over-written by another CSS rule. But the new CSS colors comes after the old colors so in the order of hierarchy, it should take precedence. Any ideas on what I'm doing wrong?
Here's my CSS code:
.main-nav li a {
font-size: .9em;
text-decoration: none;
font-weight: bold;
text-transform: uppercase;
color: #444135;
display: inline-block;
margin: 24px 12px;
background: #AFE4B3; /* Old browsers */
background: -moz-linear-gradient(#C8F1CA, #D3F1D5 , #AFE4B3); /* FF3.6+ */
background: -webkit-gradient(#C8F1CA, #D3F1D5 , #AFE4B3); /* Chrome,Safari4+ */
background: -webkit-linear-gradient(#C8F1CA, #D3F1D5 , #AFE4B3); /* Chrome10+,Safari5.1+ */
background: -o-linear-gradient(#C8F1CA, #D3F1D5 , #AFE4B3); /* Opera 11.10+ */
background: -ms-linear-gradient(#C8F1CA, #D3F1D5 , #AFE4B3); /* IE10+ */
background: linear-gradient(#C8F1CA, #D3F1D5 , #AFE4B3); /* W3C */
border-radius: 10px;
padding: 7px;
width: 100px;
}
.active {
background: -moz-linear-gradient(#FF6440, #FF8E73 , #FF6440); /* FF3.6+ */
background: -webkit-gradient(#FF6440, #FF8E73 , #FF6440); /* Chrome,Safari4+ */
background: -webkit-linear-gradient(#FF6440, #FF8E73 , #FF6440); /* Chrome10+,Safari5.1+ */
background: -o-linear-gradient(#FF6440, #FF8E73 , #FF6440); /* Opera 11.10+ */
background: -ms-linear-gradient(#FF6440, #FF8E73 , #FF6440); /* IE10+ */
background: linear-gradient(#FF6440, #FF8E73 , #FF6440); /* W3C */
}
And here's the HTML that it is being applied to:
<nav class="main-nav">
<ul>
<li><a class="active" href="index.php">Home</a></li>
<li>Library</li>
<li>Contact</li>
</ul>
</nav>
Here's a fiddle of the problem: http://jsfiddle.net/6udt8/
Thanks in advance!
.active is less specific than .main-nav li a so make it more specific by writing
nav ul li a.active {
/* Styles goes here */
}
Or even more specific...
nav.main-nav ul li a.active {
/* Styles goes here */
}
Demo
As commented, that why does this really happen? So let me explain you that, the issue is the selectors specificity here, lets make a demonstration example...
But first lets take a look at what docs have to say...
From W3C 6.4.3 Calculating a selector's specificity
A selector's specificity is calculated as follows:
count 1 if the declaration is from is a 'style' attribute rather than a rule with a selector, 0 otherwise (= a) (In HTML, values of an
element's "style" attribute are style sheet rules. These rules have no
selectors, so a=1, b=0, c=0, and d=0.)
count the number of ID attributes in the selector (= b)
count the number of other attributes and pseudo-classes in the selector (= c)
count the number of element names and pseudo-elements in the selector (= d)
The specificity is based only on the form of the selector. In
particular, a selector of the form "[id=p33]" is counted as an
attribute selector (a=0, b=0, c=1, d=0), even if the id attribute is
defined as an "ID" in the source document's DTD.
Concatenating the four numbers a-b-c-d (in a number system with a
large base) gives the specificity.
Don't get what the docs say? Don't worry, read ahead, I've shared a simple explanation which is followed by an article which will explain you the specificity calculation.
Suppose we a simple span element in a class...
<span class="hello">This is just a dummy text</span>
And we use an element selector like say
span {
color: red;
}
Obviously it will color it red... Demo
Now lets declare another selector like
span.hello {
color: green;
}
And place that in your stylesheet, and so now, that will turn the text of the span color to green... (Regardless of the order you place the property block in your stylesheet)
Demo 2 (Text will be now green)
It's because span.hello {} IS MORE SPECIFIC compared to a simple element selector which is span {}.
For more detailed explanation, I would like you to read on CSS Specificity
You can also use CSS Specificity Calculator to compare selectors specificity.
The example I shared of span, here, the specificty of the selector will be only 1
Whereas span.hello specificity will sum up to 11
http://jsfiddle.net/6udt8/2/ updated fiddle as follows
.main-nav li a.active {
background: -moz-linear-gradient(#FF6440, #FF8E73 , #FF6440); /* FF3.6+ */
background: -webkit-gradient(#FF6440, #FF8E73 , #FF6440); /* Chrome,Safari4+ */
background: -webkit-linear-gradient(#FF6440, #FF8E73 , #FF6440); /* Chrome10+,Safari5.1+ */
background: -o-linear-gradient(#FF6440, #FF8E73 , #FF6440); /* Opera 11.10+ */
background: -ms-linear-gradient(#FF6440, #FF8E73 , #FF6440); /* IE10+ */
background: linear-gradient(#FF6440, #FF8E73 , #FF6440); /* W3C */
}

How can I cut down on gradient errors?

I just tried validating a large css file and ended up with 89 errors! To save time I tried using a cross browser gradient generating tool at color zilla. These generated gradients ended up causing about 90% of my errors:
background: rgb(56,115,160); /* Old browsers */
background: -moz-linear-gradient(top, rgba(56,115,160,1) 0%, rgba(55,107,147,1) 100%); /* FF3.6+ */
background: -webkit-gradient(linear, left top, left bottom, color-stop(0%,rgba(56,115,160,1)), color-stop(100%,rgba(55,107,147,1))); /* Chrome,Safari4+ */
background: -webkit-linear-gradient(top, rgba(56,115,160,1) 0%,rgba(55,107,147,1) 100%); /* Chrome10+,Safari5.1+ */
background: -o-linear-gradient(top, rgba(56,115,160,1) 0%,rgba(55,107,147,1) 100%); /* Opera 11.10+ */
background: -ms-linear-gradient(top, rgba(56,115,160,1) 0%,rgba(55,107,147,1) 100%); /* IE10+ */
background: linear-gradient(top, rgba(56,115,160,1) 0%,rgba(55,107,147,1) 100%); /* W3C */
filter: progid:DXImageTransform.Microsoft.gradient( startColorstr='#3873a0', endColorstr='#376b93',GradientType=0 ); /* IE6-9 */
My errors read:
391 #nav Value Error : background Too many values or values are not recognized : -moz-linear-gradient(top,rgba(21,60,91,1 ) 0%,rgba(43,63,81,1 ) 100% )
392 #nav Value Error : background Too many values or values are not recognized : -webkit-gradient(linear,left top,left bottom,color-stop(0%,rgba(21,60,91,1 ) ),color-stop(100%,rgba(43,63,81,1 ) ) )
393 #nav Value Error : background Too many values or values are not recognized : -webkit-linear-gradient(top,rgba(21,60,91,1 ) 0%,rgba(43,63,81,1 ) 100% )
394 #nav Value Error : background Too many values or values are not recognized : -o-linear-gradient(top,rgba(21,60,91,1 ) 0%,rgba(43,63,81,1 ) 100% )
395 #nav Value Error : background Too many values or values are not recognized : -ms-linear-gradient(top,rgba(21,60,91,1 ) 0%,rgba(43,63,81,1 ) 100% )
396 #nav Value Error : background Too many values or values are not recognized : linear-gradient(top,rgba(21,60,91,1 ) 0%,rgba(43,63,81,1 ) 100% )
397 #nav attempt to find a semi-colon before the property name. add it
397 #nav Property progid doesn't exist : DXImageTransform
397 #nav Parse Error DXImageTransform.Microsoft.gradient( startColorstr='#153c5b', endColorstr='#2b3f51',GradientType=0 );
The gradients look great across all browsers. Should I be concerned about these errors?
If so, what's my best option here?
You shouldn't be worried about those errors. Because they're vendor-specific they won't validate. I'd suggest not checking for vendor-specific prefixes next time you validate.
Don't expect your CSS to fully validate with a W3C validator. See http://na.isobar.com/standards/#_css_validation

DotLess (.less) master.less file for variables and functions

Is there any way to utilize a master.less file to house all of the necessary config parameters for .less?
I've got the following variables that I currently have to put at the top of each .less file in my solution.
/* DOTLESS VARIABLES AND REUSABLE FUNCTIONS */
#brand_color: #9fdf40; /* Primary MySite Green */
#Color: #696969; /* Alternate Text Color */
#top_gradient: #80cc15; /* MySite Green for TOP of GRADIENT */
#bottom_gradient: #9fdf40; /* MySite Green for BOTTOM of GRADIENT */
#borders: #696969; /* Standard Gray Border */
#light_borders: #DDD; /* Lighter Gray Border */
#note: #ffffbe; /* Yellow Notification Color (Also used for ad highlights) */
#font_family: Verdana, Arial, Helvetica, sans-serif; /*Standard MySite Font Family*/
.two-corner-radius(#radius){
-webkit-border-top-left-radius: #radius; /* Saf4+, Chrome */
-moz-border-radius-topleft: #radius; /* FF3.6+ */
border-top-left-radius: #radius; /* CSS3 */
-webkit-border-bottom-right-radius: #radius; /* Saf4+, Chrome */
-moz-border-radius-bottomright: #radius; /* FF3.6+ */
border-bottom-right-radius: #radius; /* CSS3 */
}
.gradient(#from:#top_gradient, #to:#bottom_gradient, #fallback:#brand_color) {
#ffgradient: "-moz-linear-gradient(center bottom, {0} 37%, {1} 72%)";
#wkgradient: "-webkit-gradient(linear,left top,left bottom,color-stop(0.37, {0}), color-stop(0.72, {1}))";
#iegradient: "progid:DXImageTransform.Microsoft.gradient(startColorstr='{1}', endColorstr='{0}')";
#ie8gradient: "\"progid:DXImageTransform.Microsoft.gradient(startColorstr='{1}', endColorstr='{0}')\"";
background : #fallback; /* for non-css3 browsers */
background : formatstring(#ffgradient, #from, #to); /* FF3.6+ */
background: formatstring(#wkgradient, #from, #to); /* Saf4+, Chrome */
filter: formatstring(#iegradient, #from, #to); /* IE6,IE7 */
-ms-filter: formatstring(#ie8gradient, #from, #to); /* IE8 */
}
/* END REUSABLE FUNCTIONS*/
Now obviously this is easier to maintain over having to edit each instance of each variable within the css (as one traditionally would), however it would be much more beneficial if I could declare a master.less file to hold the variables and functions, and then have it rain down sweet CSS goodness to all of my "sub" .less files.
I'm currently using Chirpy to manage my .less files, which in turn uses a dotless.core.dll
Turns out there's an #import declaration that allows me to import my master.less file. All I have to do is put this at the top of each .less file and use all of the functions/variables contained within it.
#import "E:\Projects\MyApp\UI\Assets\Css\master.less";
Works like a champ.

Can -ms-filter styles be themeable in SharePoint?

We have the following themeable styles to have a gradient for the background of the webpart body:
.ms-wpContentDivSpace{
/* For Non-CSS3 Browsers */
background: /* [ReplaceColor(themeColor:"Light2-Lightest")] */ transparent;
/* For Firefox 3.6+ */
background: -moz-linear-gradient(top,
/* [ReplaceColor(themeColor:"Light2-Lightest")] */ #FEFEFB,
/* [ReplaceColor(themeColor:"Light2-Lighter")] */ #E9E9E9);
/* For WebKit (Safari, Chrome, etc.) */
background: -webkit-gradient(linear, left top, left bottom,
from(/* [ReplaceColor(themeColor:"Light2-Lightest")] */ #FEFEFB),
to(/* [ReplaceColor(themeColor:"Light2-Lighter")] */ #E9E9E9));
/* For Internet Explorer */
filter: progid:DXImageTransform.Microsoft.gradient(GradientType=0,
startColorstr=/* [ReplaceColor(themeColor:"Light2-Lightest")] */ #FEFEFB,
endColorstr=/*[ReplaceColor(themeColor:"Light2-Lighter")]*/ #E9E9E9);
-ms-filter:'progid:DXImageTransform.Microsoft.gradient(GradientType=0,
startColorstr=/*[ReplaceColor(themeColor:"Light2-Lightest")]*/ #FEFEFB,
endColorstr=/*[ReplaceColor(themeColor:"Light2-Lighter")]*/ #E9E9E9)';
}
All of it works fine except for the -ms-filter style for IE8. I've tried every combination of escaping the quotes and slashes and single vs double quotes, but the only way I can get it to work is to remove the ReplaceColor instructions:
.ms-wpContentDivSpace{
/* For Non-CSS3 Browsers */
background: /* [ReplaceColor(themeColor:"Light2-Lightest")] */ transparent;
/* For Firefox 3.6+ */
background: -moz-linear-gradient(top,
/* [ReplaceColor(themeColor:"Light2-Lightest")] */ #FEFEFB,
/* [ReplaceColor(themeColor:"Light2-Lighter")] */ #E9E9E9);
/* For WebKit (Safari, Chrome, etc.) */
background: -webkit-gradient(linear, left top, left bottom,
from(/* [ReplaceColor(themeColor:"Light2-Lightest")] */ #FEFEFB),
to(/* [ReplaceColor(themeColor:"Light2-Lighter")] */ #E9E9E9));
/* For Internet Explorer */
filter: progid:DXImageTransform.Microsoft.gradient(GradientType=0,
startColorstr=/* [ReplaceColor(themeColor:"Light2-Lightest")] */ #FEFEFB,
endColorstr=/*[ReplaceColor(themeColor:"Light2-Lighter")]*/ #E9E9E9);
-ms-filter:"progid:DXImageTransform.Microsoft.gradient(GradientType=0,
startColorstr=#FEFEFB,
endColorstr=#E9E9E9)";
}
Is it possible to have -ms-filter support themeable styles?
UPDATE:
It actually works as expected when a theme is applied. The problem is that when no theme is selected, the gradient is blue on top and dark blue on bottom. So it seems to be working up to the first comment slash because the rendered result is the same as if the style did not specify colors:
-ms-filter:'progid:DXImageTransform.Microsoft.gradient(GradientType=0)';
You could get your theme to process the images for you - and that way you wouldn't need CSS for 3 different browsers. The themes in 2010 can recolour images (or areas in images)
e.g.
/* [RecolorImage(themeColor:"Dark2-Lighter",method:"Filling",includeRectangle:{x:0,y:467,width:1,height:11})] */ background:url("/_layouts/images/bgximg.png") repeat-x -0px -467px;
Which is pretty neat. When you apply your theme, the image (bgximg.png) will be processed and colours replaced and so on.
If you look through CoreV4.css there are examples. Or this is an okay description. Perhaps Tinting would be adequate?
Failing that, I'd try putting my Theme directives before where I use my colours, rather than in:
/* [ReplaceColor(themeColor:"Dark2",themeShade:"0.8")] */ background-color:#21374c;
Here is how we fixed it. We have two style sheets that were identical, but placed in different directories:
14\TEMPLATE\LAYOUTS\1033\STYLES\MyProject\MyStyles.css
14\TEMPLATE\LAYOUTS\1033\STYLES\Themable\MyProject\MyStyles.css
Our custom master page points to the first style sheet. That is the style sheet that is used when the Theme is Default (no theme). But when SharePoint goes to compile a selected theme, it uses the style sheet in the second directory.
We left the second style sheet alone because it was working when it is compiled into a theme. We then removed the theme directive comments from the filter styles in the first style sheet:
.ms-wpContentDivSpace{
/* For Non-CSS3 Browsers */
background: /* [ReplaceColor(themeColor:"Light2-Lightest")] */ transparent;
/* For Firefox 3.6+ */
background: -moz-linear-gradient(top,
/* [ReplaceColor(themeColor:"Light2-Lightest")] */ #FEFEFB,
/* [ReplaceColor(themeColor:"Light2-Lighter")] */ #E9E9E9);
/* For WebKit (Safari, Chrome, etc.) */
background: -webkit-gradient(linear, left top, left bottom,
from(/* [ReplaceColor(themeColor:"Light2-Lightest")] */ #FEFEFB),
to(/* [ReplaceColor(themeColor:"Light2-Lighter")] */ #E9E9E9));
/* For Internet Explorer */
filter: progid:DXImageTransform.Microsoft.gradient(GradientType=0,
startColorstr=#FEFEFB,
endColorstr=#E9E9E9);
-ms-filter:'progid:DXImageTransform.Microsoft.gradient(GradientType=0,
startColorstr=#FEFEFB,
endColorstr=#E9E9E9)';
}
We tested it out and the gradient is now working, with or without a Theme, in IE7 & 8, FF and Chrome.
Have you considered using CSS3Pie?
This is a hack for IE, which allows it to recognise certain CSS3 properties using the standard syntax. It includes gradient backgrounds.
Using CSS3Pie means you can forget about ever having to use those horrible filer and -ms-filter properties, at least for gradients.
It's also great for supporting border-radius, which is probably its most popular feature.
Hope that helps.

Resources