K
Kelly
I am trying to distribute an Access 2000 adp in a SQL Server 2000 environment
and am having difficulties with my reference to SQLDMO. The adp runs fine on
the development pc but when I copy it to the network, the code won't compile
and the reference to SQLDMO is MISSING (event though the dll is there in the
exact same place). SQL Server 2005 components are installed in in the
development pc and it has been running Office 2007 side by side with Office
2000 (I have it temporarily uninstalled to try to get this working). Can late
binding be used for SQLDMO objects so that I don't have to have the reference
at all? I'd like to continue using Office 2007.
and am having difficulties with my reference to SQLDMO. The adp runs fine on
the development pc but when I copy it to the network, the code won't compile
and the reference to SQLDMO is MISSING (event though the dll is there in the
exact same place). SQL Server 2005 components are installed in in the
development pc and it has been running Office 2007 side by side with Office
2000 (I have it temporarily uninstalled to try to get this working). Can late
binding be used for SQLDMO objects so that I don't have to have the reference
at all? I'd like to continue using Office 2007.