Sage 100

Anyone having any negative feedback from clients on 2017 re fonts used on GL reports? Still installed an upgrade and it previews fine, but prints garbage. I see it is called a Sage Reporting font. I'm guessing the printer doesn't know how to handle it....

Very interesting....

Beth - I just tried this, 2017, SU1, advanced and it prints fine. I have a couple of clients on 2017 and no one has reported anything. I did Trial Balance from ABC company

Argh - client sent me a scanned copy and it is, indeed, f-ed up. I asked if they were printing to Copier/Printer or just Printer, and she said it was to 2 different printers. Now I've got to grill the IT guy to see if he really ran Autorun.exe as Admin or not.

Of course he did until you prove that he didn't.....

OMG, this just gets uglier. OK, so client is getting an error when previewing the GL Detail Report that indicates the font is foreign to his machine. The Sage Reporting font IS on his machine.... but then it gets better. This is 2017 STANDARD, but I think caching is going on somewhere - I copied his 2015 version of GL Detail Report over his 2017. His 2017 GL Detail Report IS NO MORE. Yet when he runs it - it's still the 2017 version.

What about other users/workstations? Are they Std or Adv?

Std. Had client power off and back on and now the reports are printing, although the GL Detail is still in the new font, which shouldn't exist anywhere... I'm backing off and letting the dust settle to see what other whacked thing can happen there. UGH.

I've seen a report cache in the Windows virtual store. Search the user's C-drive for *.rpt and see what shows up.

I had both users power off their machines and the reports are all working now. But the whole thing disturbs me, since it was my first 2017 upgrade, BUT it was also a new server. Chicken and the egg time, although the issue actually seems to be with the workstation, so.... 2017 looking shady...

I am having this happen with another client who is on 2013. Created a new custom report for them, then made changes. DRASTIC changes. The old version is still printing on one of the user's machines. And another odd thing - when you export is out, normally your file name is the Crystal report name, right? Well, even on a machine where the right version is being used, there is a bunch of bogus stuff in the file name, as if it were a copy. WTH is going on with this stuff?

Search the workstation for *.rpt and you may find the rogue report cached somewhere.

Holy guano, Batman. Client has over 5K different .rpts in her temp folder. C:\Users\YourUser\AppData\Local\Temp Does anyone know if caching this is an option you can turn off? Would I WANT to turn it off?

Well, back in the day, it was certainly recommended that you clear your cache. Looks like there are good reasons to continue doing so. You can always just clear the *.rpt's there. I clear mine at least once a year.

Whether you need it or not, @JeffSchwenk ? :-)

Odd that this has suddenly become an issue at three different client locations. I'm thinking something changed within Windows....

Sometimes I just get bored...

@BethBowers , the solution for this when i ran into it was to restart the workstation, it seems when the new sage font was installed during the workstation install, it does't get properly registered until the workstation is restarted.

Yes, that worked for me too on the new one - but this is a 2013 client having the issue. And I also had it with a 2015 client.