I think I have the same problem. We run SAS code to import our month-end SQL Server database tables into SAS datasets. There are dozens of tables, with code such as this: PROC SQL dquote=ansi ; create table dd_admin_trail as (select * from ncedss.dd_admin_trail); quit; In September, all date fields in SQL Server were stored as datetime fields, and imported into SAS correctly as datetime fields. In October, a change was made to SQL Server - we upgraded to SQL Server 2008 and all date fields are now stored as "DATE" fields (I checked in SQL Server, and the fields have a "DATE" type), but they import into SAS as CHAR fields of format/length $10, which are not easy to work with in SAS code.     How can I get SAS to import these DATE fields in SQL Server into numeric date fields in SAS? Shouldn't that just happen by default?   I found a way to force SAS to do this, by hard-coding a couple of date fields like in this code, but there are dozens of date fields across dozens of SQL Server tables, and I don't want to write this DBSASTYPE clause for EVERY one of them! PROC SQL; create table DD_ADMIN_TRAIL as select * from ncedss.DD_ADMIN_TRAIL (dbsastype=(ASSIGNED_TO_DT='DATE' CDC_BASE_DT='DATE') ); quit; ... View more

christinagting0: Did you figure out how to handle this? If I am understading your issue correctly, I had the same problem, too -- PROC IMPORT was reading Excel data, and not setting the length for a SAS character column long enough to store the entire string.   In my case, I solved it by setting the value of GuessingRows. By default, GuessingRows is 20, which means SAS uses the first 20 rows of the Excel spreadsheet to determine whether the data within a column is character or numeric, and what its length should be. If you have a longer character string in the 100th row, say, than in any of the first 20 rows for a column in Excel, SAS will not set the character length long enough to store it in SAS, and it will be truncated.   Unfortunately, you don’t enter the GUESSINGROWS statement into the program. You enter it in your own SAS registry, within SAS 9.4 itself. You only need to do this once.   So, open SAS 9.4, and in the command line – in the upper left corner of the screen – type regedit. Then navigate to Products-->BASE-->EFI-->GuessingRows and set the value to the number of rows in the CSV or Excel file you want SAS to scan to find the longest value. I chose 1000, because I knew I wouldn't have more than 1000 rows in an Excel file, but you could increase it up to 2147483647 (or MAX), although SAS documentation recommends not to, as it might adversely affect performance. I saw no performance hit ater I changed it to 1000.   ... View more

I'm late to the conversation, but I had a similar error as the original poster. I inherited a Windows 7 computer with SAS 9.3, SAS 9.4, and SAS Enterprise Guide 7.1 on it. I uninstalled SAS 9.3, and SAS EG stopped working.   SAS EG must have been pointing to the SAS 9.3 installation, and I wasn't sure how to make it use the SAS 9.4 installation. Finally found the answer here. I had to open a DOS command window (as Administrator), navigate to the SAS 9.4 directory (usually C:\ProgramFiles\SASHome\SASFoundation\9.4) and type sas.exe -regserver. And SAS EG works now, using my local installation of SAS 9.4 as its local Server. (I didn't have to make any changes in SAS EG to set up a profile or anything!) ... View more

Thanks, Tim_SAS! With your suggestion, I was able to get my program working with ODS statements. It's also working in a slightly different version using the DATA _NULL_ and PUT statements method I mentioned above. Not sure which way I prefer, but at least I have the option.   The thing that was confusing me was that I was assuming the Paragraph event was being triggered, but it wasn't - based on your analysis, it was the Text_group, Text_row and Text events. I didn't realize you could determine the events that were triggered by using the eventmap tagset. I'll have to look up how to use the eventmap tagset sometime.   Anyway, the ODS code that works is this (basically, I'm nullifying the Text_group, Text_row and Text events, so I'm only writing the "value" from my ODS TEXT= statement): proc template; define style styles.test; parent=styles.default; style body from body / prehtml='<meta name="viewport" content="width=device-width, initial-scale=1"> <link rel="stylesheet" href="https://demos.jquerymobile.com/1.4.5/css/themes/default/jquery.mobile-1.4.5.min.css"> <script src="https://demos.jquerymobile.com/1.4.5/js/jquery.js"></script> <script src="https://demos.jquerymobile.com/1.4.5/js/jquery.mobile-1.4.5.min.js"></script>)'; end; define tagset tagsets.mytagset; parent=tagsets.html4; define event text_group; start: ndent; finish: xdent; end; define event text_row; start: ndent; finish: xdent; end; define event text; start: ndent; put value ; finish: xdent; put nl; end; end; run;       Then I use my new tagset to start writing to the html file:     ods tagsets.mytagset path="C:\dirname_here\" (url=none) file="test.html" style=styles.test; And write some jQuery info: ods text= '<div data-role="page"> <div data-role="header"> <h1>My Title</h1> </div><!-- /header --> <div role="main" class="ui-content"> <p>Hello world</p> <form> <input id="filter-for-listview" placeholder="Type to search..." data-type="search"> </form> <ul data-role="listview" data-inset="true" data-input="#filter-for-listview" data-filter="true">';       ...and later in the loop, I call ODS to write each list item to the HTML file:   ods text= "<li><a href='#'>&name</a></li>"; After the loop, I need to close the <ul> tag from above:   data _null_;     ods text= '</ul>';   run; ...and of course at the end, close the tagset:   ods tagsets.mytagset close; ... View more

Well, I tried a variety of ODS statements, from ODS HTML3 to ODS HTML5 to ODS MARKUP, but I could never figure out how to override the paragraph event that the ODS TEXT= statement initiates. I finally tried a different approach that worked, based on a suggestion to this other SAS Community question - Generate a totally raw HTML file.   I replaced all my ODS statements with a FILENAME statement followed by DATA _NULL_ steps with PUT statements that write all my HTML tags directly to the .html file. It's a brute force approach, but it worked for me ... View more