R
Roger Thomas
My Access XP project is programmed to allow users to
import text files. The code relies on SQL Server's Data
Transformation Services. I have set the appropriate
reference in VBA to the DTS Package Object Library.
The import process works fine on my development computer.
It causes runtime errors on client computers once it
encounters code that sets a reference to my package object
(I'm using late binding), even though they have the
appropriate reference set to dtspkg.dll.
One difference is that my design computer has SQL Server
Client Tools installed, which makes the dtspkg.dll object
library available to me. We are not allowed to install
the Client Tools on the client machines, so I am stuck
with manually copying the dll. I've tried copying it to
the directory that contains msaccess.exe and the directory
that contains the database file, to no avail.
Do I have to register the dll with the client's registry?
I tried Start/Run and msaccess.exe /regserver, but that
creates a reference to dtspkg.dll in the SQL Server
directory that doesn't exist. And I'm not allowed
permissions to view/edit my client's (or my own) registry.
Somehow, some way, I'm sure it's possible for my client's
version of the database to recognize the object library
and execute my code. Heeeeeeeeellllllllllp.
import text files. The code relies on SQL Server's Data
Transformation Services. I have set the appropriate
reference in VBA to the DTS Package Object Library.
The import process works fine on my development computer.
It causes runtime errors on client computers once it
encounters code that sets a reference to my package object
(I'm using late binding), even though they have the
appropriate reference set to dtspkg.dll.
One difference is that my design computer has SQL Server
Client Tools installed, which makes the dtspkg.dll object
library available to me. We are not allowed to install
the Client Tools on the client machines, so I am stuck
with manually copying the dll. I've tried copying it to
the directory that contains msaccess.exe and the directory
that contains the database file, to no avail.
Do I have to register the dll with the client's registry?
I tried Start/Run and msaccess.exe /regserver, but that
creates a reference to dtspkg.dll in the SQL Server
directory that doesn't exist. And I'm not allowed
permissions to view/edit my client's (or my own) registry.
Somehow, some way, I'm sure it's possible for my client's
version of the database to recognize the object library
and execute my code. Heeeeeeeeellllllllllp.