K, yes, I see now. Mystyle was based on the minimal style and that style doesn't have graph stuff. Even though I added that code in mystyle it didn't seem to be acknowledge or something. So I switched to rtf as a parent. I then had to add a few style fonts missing in mystyle, but then suddenly the graphfont is being taken into account.   So, thanks a lot! 😃 ... View more

That's what I tried to explain above. Let me paste it here and try to expand on it. --- For example, for the following code, I would use the mprint lines to replace the %vchk calls. The code would go from this: create table titi4 as select a.titi %vchk(in=titi1,var=toto,sql=1,alias=a) %vchk(in=titi2,var=tata,sql=1,alias=b) from titi1 as a left join titi2 as b on a.titi=b.titi; quit;   To this, where %vchk(in=titi2,var=tata,sql=1,alias=b) is replaced with the mprint line: create table titi4 as select a.titi %vchk(in=titi1,var=toto,sql=1,alias=a) , tata from titi1 as a left join titi2 as b on a.titi=b.titi; quit;   Because I have no mprint line for  %vchk(in=titi1,var=toto,sql=1,alias=a) I cannot replace it with anything that matches that particular macro call. The option I have left is to assume that if I have nothing to match then it probably means the macro generated nothing. But I don't like to assume. ---   Basically, it's just a question of having a resulting code to match with any macro call. If I have no resulting code for any one macro call then, as mentioned above, I start assuming that the macro didn't have anything to output. Instead of assuming I'd prefer to be certain by having a one-to-one match between macro calls and resulting codes. Hopefully that makes sense. ... View more

A good suggestion indeed. 😃 Maybe I should explain my reasoning a bit more. My task is to create a macro that can extract the code from the log, but in such a way that all macro variables used in the code are resolved (symbolgen lines) and all macro calls are replaced with the code lines (mprint lines). The goal is to produce a code the client can run without having access to the macros and such. I managed to achieve that with the first program with which I was working. However, the second program was having the split mprint lines and the issue with such lines is that unlike standard code lines they don't start with a ! and stuff. I had to find a way to put back together those split lines which I eventually did. However, it seems safer to me to not have to sew lines back together in the first place. The macro I wish to update isn't itself overly complex to begin with. Therefore, the added complexity seems acceptable if in the end I can more reliably put the program back together from the log. ... View more