About BenConner

BenConner · ‎01-17-2017

Hi Cynthia, LOL... that was the one combination I hadn't tried. Just wasn't creative enough. Thank you so much! The target in this case is about 5000 pdf files. --Ben

DanH_sas · ‎01-17-2017

If you are on Windows, I would use ACTXIMG. On other platforms, you would need to use JAVAIMG.

BenConner · ‎01-12-2017

Just found out what it was; a previous proc in the job had specified a width and height on an ods graphics statement. Adding: ods graphics on / width=5in height=1.75in; did the trick. Thanks! --Ben

BenConner · ‎01-11-2017

Hi Cynthia, That did it! I was even able to increase the font size a hair for readability and it still all came out. Thank you so much! --Ben

BenConner · ‎01-04-2017

Would love to; this is a government-approved document I'm trying to match. Exactly. Found the root cause today: I was printing it in Acrobat Reader with the default 'fit to page'. Arghhh... Should have been using the 'Actual size' setting. Once that was changed...it printed fine. Thanks for replying! --Ben

BenConner · ‎12-02-2016

Looks like the schema wasn't included in the default definition we use to access the DB; I have to include it explicitly. So the code KSharp provided told me what schema they had given to it. Thanks to all with this! --Ben

BenConner · ‎10-18-2016

While I wasn't able to find a solution to the original question, I found a way to get (mostly) the same thing done: x " ""C:\Program Files\SASHome\SASFoundation\9.4\sas.exe"" -sysin ""&runpath\test1.sas"" -log ""&runpath\test1.log"" "; also works nicely for kicking off an external SAS run. Coupling it with noxwait and noxsync then allows a controlling SAS sheduler to spawn off different SAS runs at will without getting held up waiting for each to complete. This was the final goal. Thanks! --Ben

BenConner · ‎09-03-2016

Ok, that's just plain slick. 🙂 Outstanding! Thank you so much! It does exactly what I was looking for. Just couldn't put it quite together. This will help a lot on the actual project I'm working on. --Ben

BenConner · ‎09-01-2016

This took a good while to research, but the issue relates to having the width and height specified on the region statement. Removing these two parameters made the problem go away. It shouldn't have been an issue but is in the current release. In my case it was workable as I have white backgrounds on the region anyway and it worked just fine. --Ben

Ksharp · ‎08-04-2016

Sorry. I don't know. I am not familiar with ODS LAYOUT.

BenConner · ‎07-28-2016

Found the issue. There is a row_gutter= value as well that I didn't set. Making that = to 0in did the trick. --Ben

BenConner · ‎07-20-2016

Good morning, It does appear it was an issue with how the transparency layer was defined in the image. Used a different graphics package that I know better and it worked as advertised. Including as a .png file. Sorry for the confusion! --Ben

BenConner · ‎07-19-2016

Hi Cynthia, I have that one in a collection on my desk as well as the wonderful ones you have written. Chevell in T.S. found the key to what was happening: apparently to get it to work I also need the cellheight=xxin option as well. that tells the style interpreter how high the area is it needs to center. That seems awkard that it doesn't default to the region height. Even a warning would be nice. But as long as I can control it, I'm good. So the final ODS TEXT statement would be: ods text = "^{style=[vjust=center just=center cellheight=3in] Test Title}"; Thanks! --Ben

BenConner · ‎07-15-2016

Got a reply from Bari Lawhorn in SAS T.S. She pointed me to the usage note: http://support.sas.com/kb/46/333.html SAS' implementation of PDF output requires setting the DPI resolution to 150 for best results. The graph I had been given was 330. After resizing it, as an added bonus the file was a lot smaller as well. What irks me is that many weeks ago in the first stages of learning this stuff, I had run across this usage note, read it, and tucked it away. In a very safe place. Sigh... Once the image was resized, it looked great! --Ben

BenConner · ‎07-11-2016

Thanks, Cynthia! This is a good example of taking a graphic image that originally was coded as a series of Drawtext and Drawrectangle GTL statements and converting it to a simpler Proc Report. The original approach actually had 10 of these images plus some additional text information. While I don't have an issue with GTL, drawtext statements do not recognize dynamic variables and as a result the SGRender proc can't take advantage of a BY statement when you have a lot of these to generate. By finding a Proc Report solution, they can be created with one execution of Proc Report and the output directed to a Document Store, and the final output assembled later as needed. Much appreciated! --Ben

Online Status	Offline
Date Last Visited	‎06-06-2023 11:03 PM

Re: execution timing of macro generated code vs macro invocation.

execution timing of macro generated code vs macro invocation.

Re: "File is in use" error when reading an external file

Re: Insertbuff= option for SAS SQL Pass-through?

Re: Insertbuff= option for SAS SQL Pass-through?

Re: Insertbuff= option for SAS SQL Pass-through?

Re: Insertbuff= option for SAS SQL Pass-through?

Re: Insertbuff= option for SAS SQL Pass-through?

Re: Insertbuff= option for SAS SQL Pass-through?

Insertbuff= option for SAS SQL Pass-through?

Re: member level reading in ZIP Access method doesn't work with fileva...

Re: ODBC to MS SQL server permissions

Re: Proc Report refinement with style and title management

Re: how to read filenames of a directory into a file

Re: ERROR: Key not found. when using hash tables...how to suppress?

Re: SAS Support policies

Re: Thoughts on using SAS compression

Re: Executing SQL Server procs from SAS

Re: Mixing SPDE files with non-SPDE SAS datasets

Re: Does excel destination use only one by variable with the sheet_int...

Re: Assigning a color to a unicode symbol in ODS Text string

Re: work.gseg doesn't exist error when trying to replay a gmap graph f...

Re: Using the entire region for a drawspace in ODS GTL

Re: Positioning issue with Proc Report in ODS Layout

Re: ODS Layout positioning in PDF files

Re: ODBC to MS SQL server permissions

Re: Can you stack commands in an 'x' statement in Windows?

Re: Proc Report refinement with style and title management

Re: ods region layout question

Re: Justifying text segments in an ODS TEXT statement

Re: Working with Absolute and Gridded layouts together

Re: ODS Graphics problem with transparent background

Re: vjust usage in a region

Re: pixels per inch and other mysteries

Re: Using unicode characters in data values in Proc Report