Cannot drop article ''TABLE60'' from publication ''DB_Comp''...

[ Merge Replication ]
I work with a software that the act deletion and creation of the table
and deletion and creation and change of the field by the users happens
so much.
for deletion of the table using this command :
sp_dropmergearticle @.publication='DB_Doc',
@.article = 'TABLE65',
@.force_invalidate_snapshot=1
, but after execute this command displayed below message :
"Cannot drop article 'TABLE65' from publication 'DB_Doc' because its
snapshot has been run and this publication could have active
subscriptions."
how can i drop the table in active merge replication with T-SQL(System
Stored Procedure)?
thanks.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
As far as I know, you can't. The best you can do is synchronize all
subscribers until no change is applied, drop the publication, change the
table on the publisher and subscribers, readd the publication and do a
nosync initialization.
Rgds,
Paul Ibison

Cannot Crete server object

I'm using a client software to connect to a server. Everytime I try to log in
to that software an error: " ERROR 70: Cannot Create Servre Object". I
currently use a Microsoft Advanced server with the clients having a WIndows
XP OS.
What do I need to do?
Contact your Software Vendor. It is not a SQL Server error, but an error
that is only understood by the vendor.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"thescene" <thescene@.discussions.microsoft.com> wrote in message
news:8C17E98A-A16F-4EEF-AE8F-D32F851B63F7@.microsoft.com...
> I'm using a client software to connect to a server. Everytime I try to log
> in
> to that software an error: " ERROR 70: Cannot Create Servre Object". I
> currently use a Microsoft Advanced server with the clients having a
> WIndows
> XP OS.
> What do I need to do?
|||I just changed my switch, is that a possible reason why it's not working
anymore?
Joseph
"Mike Epprecht (SQL MVP)" wrote:

> Contact your Software Vendor. It is not a SQL Server error, but an error
> that is only understood by the vendor.
> Regards
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "thescene" <thescene@.discussions.microsoft.com> wrote in message
> news:8C17E98A-A16F-4EEF-AE8F-D32F851B63F7@.microsoft.com...
>
>
sql