Sage 100

Has anybody had any luck with using a TROY MICR font module with Crystal 11 to create a secure signature? I reached out to the manufacturer for instructions and was given a document from 2010. That document explains how to create a word document, setup the symbols and when printing from word the signature prints. However, the very last line of the document says "" Insert an OLE Object from the Crystal reports menu and link to the word document you saved to your Crystal report"" That is the only info it give for linking this document to the report. It doesn't work. Any Ideas would be great.

I have worked with their Fonts but not with their signature. I have done a signature like that before. It is just an OLE object in crystal report that you point to. I think what they are doing in the word document is the signature security where it will not print without pin or it will reverse it / change it to void. Now their Fonts do have issues. With Crystal you have to have a font that exists in your windows font folder. It cannot be a font in the driver (like thermal printers normally would). So you have to use font substitution. Use an actual windows font like Trebuchet MS and create a font substitution to change it to the driver or special font being used. This is only required when running the Crystal Reports Runtime. I think it is an issue introduced by .Net, If I recall. See if the process works with standalone Crystal but not the Runtime. The runtime version could be the issue. I will say Troy attempted to help with the font issue but They NEVER got it working The font substitution works for every thermal I have had to work on but the Laser Troy printers would not do the substitution. It just ignored it. The issue is happening in the driver itself, from what we can tell. We ended up using different fonts that were not Troy but put a hidden field that would trigger the PIN request on the printer. Works to secure the printer but the front changes based on Troy (instead we secure that by only installing the fronts we used on the machines that needed it, not as secure but enough for the customer). Don't know if any of that helped but who knows ;)

Hi Todd. Thanks for the information. I am not using the runtime. I am using the designer. I appreciate the info and I am working through the issue again today. I have a feeling it might be tied to network issues. The reason I think this is it is a M506 Troy printer with a MICR usb dongle. The form prints fine when working within the confines of WORD which is local. The printer is a network shared printer but on occasion when trying to click the designer button on the form I get a message saying that the form doesn't exist. If I open file exploder and go to the UNC it requires a network login. Once that is entered, I can design the form. I am thinking because of the way this IT depart has that setup that the Crystal form may not be able to grab the OLE object correctly. I will be adding the WORD micr document to a network share that has rights, changing the link in Crystal and ensuring that the printer driver can be seen as well. Again, thanks for the help it opened my mind up to other ideas. I also attached the word document from TROY just in case anybody else experiences this.

You can't have it prompt for the user and password. That is more than likely the issue.

Yes Sir. It didn't happen yesterday. I think the IT guy had already circumvented it prior to me getting on. Saw it today when we connected. I think you are 100 percent. I will start by correcting that issue now that I am aware of it.