Just installed, great product.
When I print from MS word, the default file name is the document name.
When I print from my VB application, the default file name is "Microsoft Visual Basic".
Is there a way to set the default file name to something more useful from a VB6 application?
Ken Gilbert
Hi Ken, that name is suggested because that's how the application is recognized, because you're basically printing from VB. What name do you think it should suggest by default when printing from VB, you mean it should recommend as with Word the name of the VB file?
I was just trying to understand what logic DoPDF uses to select the default file name. Clearly, MS Word somehow exposes its file name. I was wondering if there was any way for my VB application to expose the file name I would like used as the default?
we'll look into that, and if it's possible we'll use the name of the saved VB file too just as in word.
Thanks Softland. Let me know (with a post) if there is something I need to do to enable you to see the file I have open before I print.
Ken
Hi Ken, unfortunately we cannot do anything about printing from VB. The problem is that this is how VB sends the filename for printing, and we can only work with the filename it sends.
So if you have programmed a VB application that prints, maybe there's a way you can programmatically send the correct title for printing.
Thanks again Softland. I looked to see if there was a general property I could set but didn't find anything meaningful. Can you tell me what Windows system call you make to retrieve the file name or the name of the parameter passed that contains the file name? This might help me figure out how to set the file name before I invoke the printing.
Ken
You can try this code, paste it as a printer path
Dim strDesktop As String
Const ssfDESKTOP = 0
strDesktop = CreateObject("Shell.Application").NameSpace(ssfDESKTOP).Self.Path
MsgBox strDesktop
Clipboard.Clear
Clipboard.SetText strDesktop & "\Weeknr. " & txtWeekNr.Text
Sorry Lensen, but I don't understand this post.
Ken
Place the code in the vb code of your VB program before you print.
Then, in the window that the doPDF pdf file to come, click the right mouse button to paste your own path and file name into it.
In this case the file is placed on the desktop.
Kars
Thanks for the suggestion Kars, but unfortunately this does not help.
My users can already change the file name and path to whatever they want.
But this requires additional typing (or highlighting and pasting in your solution) which is unexpected and error-prone.
I'm trying to find out how DoPDF gets the default file name (currently "Microsoft Visual Basic") to see if there is some way my program can get the expected file name as the default.
Ken
@lensen - kagsw1 is right, your suggestion does not help in his case.
@kagsw1 - sorry, but what you want to do cannot be done with doPDF. We do have a commercial product for developers, nova PDF SDK, and I think would be helpful in your case, not sure if it's worth it for you (if it does and you're interested in it, we can give you a discount towards the displayed price).
Is there any way to pass file name to doPDF from Visual FoxPro, bypassing the save window?
I use SET PRINTER TO NAME "doPDF v7", this works well.
Hi,
Unfortunately you cannot bypass the window with doPDF and set the name automatically.
Thank you.
Hi forum.
I'm new to doPDF, having tried some other PDF writers and looking for something better.
When I "print" any document to doPDF, the "SavePDFfile" dialog box opens as expected.
But it seems there's NO field focus within the window ! Tabkey does nothing either.
I cannot enter any filename without first finding a desk rodent and clickety-clacking somewhere in the window.
Is this working as intended ?
How can I configure this useful tool to work simply and swiftly with just a keyboard ?
From almost any application, Alt-File, Print, doPDF, Enter, {Enter Filename}, Enter. Done.
Fast and rodent-less.
TIA's
Hi,
We managed to reproduce this behavior and we will implement a fix within the next releases.
Thank you for pointing this out.
You must log in to post.
