![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
I have attached a sample MDB and dts file which demonstrate the problem, using the SQL Server Northwind DB. It appears to only affect Access, running the code from a Word document succeeds... Microsoft didnt seem to interested. -- James Goodman "James Goodman" <james (AT) norton-REMOVEassociates (DOT) co.uk> wrote in message news:%23%23AN9oe5FHA.1864 (AT) TK2MSFTNGP12 (DOT) phx.gbl... I appear to have found a problem with the above critial update when attempting to execute a dts package from Access, which exports data from a SQL Server DB to Excel. If this update is installed, it fails. However, if the same code is called from a different VBA program it works as expected. -- James Goodman |
#2
| |||
| |||
|
#3
| |||
| |||
|
|
While I don't recommend opening attachments either, just as independent confirmation, I've scanned these files with a virus scanner AND looked at the Access code myself, and at least on the surface, the embedded files both appear to be clean. That said, I didn't look at the DTS package, except a quick visual inspection of the file data itself, as I don't have SQL Server installed on this machine. If you want to be REALLY paranoid, you also have no guaranteed way of confirming that I'm not the originator under another guise...but I'm not, honest! ![]() So, to the extent that you can trust a newsgroup post, I can tell you that the attached file was safe...take it or leave it. Rob |
![]() |
| Thread Tools | |
| Display Modes | |
| |