We are attempting to write a .pdf file using a custom font. We know that BO replaces the custom font with one of the few generic fonts it comes with. :? So we installed Adobe Distiller on a server. From full client (on the server), I execute a macro in the report which writes a postscript file, and then runs Distiller to convert it to a pdf file. That works beautifully, and I get the custom font. The problem is when we schedule the same report through BCA. BCA runs the same macro, but now the pdf file comes out with the generic font instead. I thought that BCA was simply running full client behind the scenes - if so, shouldnât it produce the same result?
Iâm not sure of the procedure to do this but I believe you should create a complement that includes your macro instead of including the macro in the report; then install the component on the server.
When you schedule the document refresh add to the list of actions the execution of the macro included in the component, and that should do.
I tested a similar schedule using a complement to send the report by mail in different formatsâŚ
Thanks for your reply. This is all news to me. Can you tell me a little bit more about these components? Are they a windows feature, or third-party software? Iâm not sure how to look it up on the webâŚ
I was just reading about add-ins and was guessing that you had meant âadd-inâ. I will have to do some more reading on it, though⌠What puzzles me is that the macro works ok from full client, then it doesnât work in BCA. I mean, the macro runs, and I get the files I expect, only the custom font isnât used⌠Maybe I should open a ticket with BOâŚ
Running the macro as an add-in or just a macro makes no difference, at least to my problem. I have been able to create a .pdf file with the custom font by writing to a PDF driver, rather than a postscript driver (using Distiller). The new problem now is that this only works in BCA when I schedule it from the machine where I have distiller installed (the server). Scheduling it from a client without distiller, I get an error. Do I need to have distiller intalled on the client as well?
We have done some more testing and now we have determined that the key to getting the macro to create a .pdf file is having someone logged on to the BCA server. We either get a file created without problems (if someone is logged on), or an error is posted on the âadobe PDFâ âprinterâ which says âerror printingâ (when the job runs but nobody is logged on). Either way the job finishes âsuccesfullyâ in BCA. Distiller apparently needs an user to be logged in. I donât know why that is, though. We canât simply leave an account logged on to the server all the time. We installed Adobe Acrobat Standard 6.0 on the BCA server, and defined a local printer (âAdobe PDFâ), which is referenced in the macro. Could it be that we are using the wrong software, and Acrobat Standard only works interactively? Do we need Distiller Server instead?
The problem is when we schedule the same report through BCA. BCA runs the same macro, but now the pdf file comes out with the generic font instead. 
I thought that BCA was simply running full client behind the scenes - if so, shouldnât it produce the same result? 