think i've just realised what im doing wrong,
i thought SQLDMO.dll & SQLDMO.rll are all that is required on the client
machine, the rest reside on the server.
ill let you know how i get on
"Chris Podmore" <Ch**********@discussions.microsoft.com> wrote in message
news:27**********************************@microsof t.com...
I have read the article and it says that more than 2 files are required.
Sqldmo.dll
Sqldmo.rll
Sqlsvc.dll
Sqlsvc.rll
Sqlwoa.dll
Sqlresld.dll
Sqlwid.dll
W95scm.dll
Plus one or all of the following depending on the protocol used:
Named Pipes: Dbnmpntw.dll
Sockets: Dbmssocn.dll
Multi-Protocol: Dbmsrpcn.dll
We have a small program with our overall application that uses SQLDMO to
manage the database schema, I have tested this installing the above files
and it works fine.
There are licencing issuses, the company I work for states to our clients
that the application that manages the database schema can only be run on a
workstation with the correct licences. We have someone here who is really up
on licencing and he has confirmed that even using the dll's internally on a
none licenced machine is breaking the licence. Licencing is very
complicated, thats why we have someone dedicated to the task.
"Craig G" wrote:
yeah licensing can be sorted if need be
but until i get this SQLDMO.dll registered everything is up sh*tcreek!!
"Jeff Johnson [MVP: VB]" <i.***@enough.spam> wrote in message
news:eh**************@TK2MSFTNGP11.phx.gbl...
"Craig G" <Ga*******@hotmail.com> wrote in message
news:Oq**************@TK2MSFTNGP12.phx.gbl...
> licensing issues aint a problem as its an internal application
There are still client access licenses required, I believe. You know,
if you were to get audited or something....