G
Guest
Hi
I have an asp.net app thrat merges to Word. It prepares an xml file by using
the old ADODB library to save a recordset (myRecordset.Save(XMLPath,
ADODB.PersistFormatEnum.adPersistXML), then downloads the file to the user
and uses client script to do the merge. Very similar to the way I did it with
ASP a few years ago.
ASP.NET version has been working very well for 9 months. User has to
configure I.E. settings tyo allow ActiveX to run from the site, and still
gets warning every time about running ActiveX.
Is there a more polished approach available (without buying expensive thrid
party tools)? Want to get rid of the vbscript if possible and want to
dispense with ADODB.
Any ideas/pointers would be appreciated.
David
I have an asp.net app thrat merges to Word. It prepares an xml file by using
the old ADODB library to save a recordset (myRecordset.Save(XMLPath,
ADODB.PersistFormatEnum.adPersistXML), then downloads the file to the user
and uses client script to do the merge. Very similar to the way I did it with
ASP a few years ago.
ASP.NET version has been working very well for 9 months. User has to
configure I.E. settings tyo allow ActiveX to run from the site, and still
gets warning every time about running ActiveX.
Is there a more polished approach available (without buying expensive thrid
party tools)? Want to get rid of the vbscript if possible and want to
dispense with ADODB.
Any ideas/pointers would be appreciated.
David