We have a number of dts packages which users can call through an
application. Most of them are used to copy data from the DB to various Excel
files.

One computer seems unable to do this, failing on all packages, at the
transform data task step. However, if the package is called directly from
SQL EM it executes succesfully on the problem machine.

The application calling the package is an Access 2002 ADP.

Any ideas?

To elaborate, the error message is in the form of:

Step 'Copy Data from <qryName> to <TargetWorksheet>' Failed.
Error: -2147213206
Source: Microsoft Data Transformation Services (DTS) Data Pump
Description: The number of failing rows exceeds the maximum specified.
(Microsoft JET Database Engine (80040e09): Cannot update. Database or object
is read-only.)





"James Goodman" <james (AT) norton-REMOVEassociates (DOT) co.uk> wrote

It definitely sounds as thought there is a permissions issue here.
Could that be the case?

Have a look at Google for some ideas.

http://www.google.com/search?sourcei... s+read%2Donly


Allan

"James Goodman" <james (AT) norton-REMOVEassociates (DOT) co.uk> wrote

Yep, I agree.

I just cannot fathom where this permission problem is coming from.

These packages have been working for several years on all machines until
recently, when this one machine has started failing.

The strange thing is that the dts package succeeds for the user on another
machine, or for the same user on the problem machine from EM, which suggests
it is somehow a combination of the application (Access ADP) and the machine.

I will keep looking...



"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote

Found it, although I am unsure of how to proceed.

Using Virtual PC I have been able to establish it is an Update to Access
2002: KB904018.

As a known issue, you cannot update tables which are linked to an Excel
file, but from what I can tell this is not the case. However, it seems kind
of similar.

Unfortunately, there does not appear to be any way to remove this update
without reinstalling office, which I presume will correct the issue.

Any suggestions as to how I make Microsoft aware of this without paying to
open a support case?


"James Goodman" <james (AT) norton-REMOVEassociates (DOT) co.uk> wrote

Link to KB:
http://support.microsoft.com/kb/904018


"James Goodman" <james (AT) norton-REMOVEassociates (DOT) co.uk> wrote

Ok, more news!

If I execute the code from another VBA program such as Microstation V8, it
works perfectly, as expected.

I cannot understand why it doesnt work in Access because there is no link
working between Access and Excel that I can see. Access calls a dts package,
which then executes...



--
James Goodman



"James Goodman" <james (AT) norton-REMOVEassociates (DOT) co.uk> wrote