in reply to printing database rows in a file

What you’d really like to do, of course, is either to send the items as a zipped-up attachment, or, better yet, provide an internal web-page that users could link to to view the data.

If you can store the data in a read-only file in a place where everyone can see, just send them an e-mail with a hotlink to it ...   A “UNC” fileref of the form \\servername\filename\ eliminates issues of drive-letter assignments, if you know that every intended recipient can reach and access the referenced file.

The question really should be asked (by someone if not by you), whether such a voluminous output is really useful and satisfactory to the business needs of its recipients.   I seriously doubt that it is.

Replies are listed 'Best First'.
Re^2: printing database rows in a file
by Anonymous Monk on Oct 22, 2010 at 06:41 UTC

    At least in my case, Certainly such a voluminous data is useful for the business to review how much junk data got inserted into the system and take necessary actions on that.