Laurence,
This is part three that lets you hide the header...
http://www.kalengibbons.com/blog/index.php/2009/04/custom-printing-with-flex-part-3-printing-data/
*source code* also available
On Sat, Sep 4, 2010 at 7:05 AM, Eric DeCoff ericdec...@gmail.com wrote:
Laurence,
Back Home
Thanks for the info, Eric...
Unfortunately that solution still appears to require user-interaction of
some sort... You can't just hit Print and have it go to the printer that
you want it to go to. Unless, of course, the printer is shared on the
network and available to the server -- so it's the
So... With all this discussion of printing from Flash Player and whatnot,
it seems almost certain that we're going to have to switch to AIR...
Has anyone here ever taken a fairly mature app from Flash Player to AIR?
I'm certain it can't be as simple as checking the AIR App button in the
FB4
To clarify, I'm aware that FB4 has a convert from Flash to AIR wizard...
I don't trust wizards to actually do the right thing, in most cases... In
fact, I generally find that they break more than they fix... So, I guess
I'm asking for your experiences with this wizard, if you have any...
Laurence,
Have you concidered using Microsoft reporting features?
sent via droid
On Sep 4, 2010 5:10 PM, Laurence MacNeill laurence5...@gmail.com wrote:
Thanks for the info, Eric...
Unfortunately that solution still appears to require user-interaction of
some sort... You can't just hit
You mean from the MSSQL database? I'm unfamiliar with the reporting
features from there, but it would seem to me to be the same situation as PHP
and CF -- I need control of a client computer's printer(s). A server-side
solution isn't going to work. And I seriously doubt that the MSSQL
reporting
Laurence,
Here a link to SQL server client side printing
http://msdn.microsoft.com/en-us/library/ms155874(SQL.90).aspx
sent via droid
On Sep 4, 2010 6:00 PM, Laurence MacNeill laurence5...@gmail.com wrote:
You mean from the MSSQL database? I'm unfamiliar with the reporting
features from
Two problems with that - #1, we use SQL 2000, not SQL 2005 or 2008 (doesn't
seem like they offer a version of that library for SQL 2000, from what I can
tell). Second, it still requires user interaction... It's basically a
custom print-dialog box -- any print-dialog box is a bad thing for us.
