O
ontiK
Guest
Hi All,
This one is driving me nuts.
My App is an Access XP adp on a SQL backend. I have some querys that take an eternity to run and typically timeout when I try and run them from the Access client. I can however export the data via DTS which is good because a data export is what I want to achieve, but bad because it takes sometime 20mins to run.
However, what I need to do is have the user be able to push a button on the client that starts an export on the Server which then mails the exported data as an attachement to the user who executed it. The user needs to be able to coninute working while the server is doing its thing. I have played with xp_sendmail but the format of the data in the attachment it creates is inappropriate. (Needs to be csv at least or Excel at best. xp_sendmail attachements have a controlled line size via the @witdh param)
This functionality also needs to be dynamic so I need to be able to change the view or table name the export will come from and provide a WHERE clause. This rules out using bcp because it is limited as to how many sets of quotation marks (single and double) you can include in your SQL command param. I'm not really in a position to be able to build a DTS package for every possible export either so my options are getting slim.
Has anyone got any suggestions for paths to follow to try and meet this objective?
Regards,
ontiK.
This one is driving me nuts.
My App is an Access XP adp on a SQL backend. I have some querys that take an eternity to run and typically timeout when I try and run them from the Access client. I can however export the data via DTS which is good because a data export is what I want to achieve, but bad because it takes sometime 20mins to run.
However, what I need to do is have the user be able to push a button on the client that starts an export on the Server which then mails the exported data as an attachement to the user who executed it. The user needs to be able to coninute working while the server is doing its thing. I have played with xp_sendmail but the format of the data in the attachment it creates is inappropriate. (Needs to be csv at least or Excel at best. xp_sendmail attachements have a controlled line size via the @witdh param)
This functionality also needs to be dynamic so I need to be able to change the view or table name the export will come from and provide a WHERE clause. This rules out using bcp because it is limited as to how many sets of quotation marks (single and double) you can include in your SQL command param. I'm not really in a position to be able to build a DTS package for every possible export either so my options are getting slim.
Has anyone got any suggestions for paths to follow to try and meet this objective?
Regards,
ontiK.