D
Dan M
Using Access XP adp file with SQL Server 2K back end.
Development machine has Access SP-3, SQL Server client
tools. Clients have Access SP-2, no client tools.
VBA code creates a DTS package and imports data. Works
fine on development machine, not on clients. They need
dtspkg.dll.
Is it true that simply providing a copy of the dll for the
client to store on their hard drive is not enough?
Must the dll be registered in their O/S (mostly Win 2000,
some Win 98)?
If I must register dtspkg.dll, how the heck do I do that?
On client PC, tried to simply set a reference to the
DTSPackage Object Library in VB Editor using the Browse
feature of the References dialog, it won't take (the
reference simply never appears ANYWHERE in the list).
Tried same on development PC, having made a copy of dll in
the directory that stores the adp file, but same thing
happens. Reference in ProgFiles\SQL Server\80 etc works
fine on development machine, but clients don't have that
directory.
Any insight would be greatly appreciated. I've been
reading KB articles all day with no luck.
Development machine has Access SP-3, SQL Server client
tools. Clients have Access SP-2, no client tools.
VBA code creates a DTS package and imports data. Works
fine on development machine, not on clients. They need
dtspkg.dll.
Is it true that simply providing a copy of the dll for the
client to store on their hard drive is not enough?
Must the dll be registered in their O/S (mostly Win 2000,
some Win 98)?
If I must register dtspkg.dll, how the heck do I do that?
On client PC, tried to simply set a reference to the
DTSPackage Object Library in VB Editor using the Browse
feature of the References dialog, it won't take (the
reference simply never appears ANYWHERE in the list).
Tried same on development PC, having made a copy of dll in
the directory that stores the adp file, but same thing
happens. Reference in ProgFiles\SQL Server\80 etc works
fine on development machine, but clients don't have that
directory.
Any insight would be greatly appreciated. I've been
reading KB articles all day with no luck.