Why not just have a script that changes layout to a "printer friendly" layout and then perform a find for the desired records? Wouldn't that accomplish the same thing for you?
Unfortunatley not for the instant web publishing users. When you use instant web publishing users are restricted to "browser level" printing. This means that they can only print what is currently on the screen. So if you have a report designed in "list view" with a found count greater than 25, you can only print the first page of the report.
So I'm trying to find a way around this printing issue. What do you think?
I thought that might be the case, but wanted to be sure. What's unclear to me is what kind of "Printer friendly" layout will even be possible here.
Perhaps, if the data is static, you could link to a PDF of the data. If it's not, then I don't see a way to do this in IWP--but IWP is something for which my experience is limited.
That's why I'm inquiring about the ASP to Filemaker connection. If I have a web designer knock out some stand alone web pages that I then store in the web root of the server, I think I can call the external pages from IWP using the "open url" script step.
This would pass the parameters of the found set to the external page via ODBC. The idea is to push the data to an external page which would allow for printing. But all the articles that I've seen about this are old and at the desktop level with a Filemaker remote access plugin. I'm wondering if this can be done at the server level.
Trying to get some sort of feedback before I go out and hire a web designer to draft test pages. If it can't happen, no point in wasting a project deposit.
I almost posted "but you can't pass the found set in Open URL", but then I remembered a section of the Filemaker Training Series that describes using a Web Viewer to create a table of data as a single page "cross tab" report. Since that URL type code can push data to the web viewer, it looks, in theory like you might be able to do this with Open URL.