ConnectionObject is the connection you are using to connect to the db... I gues this should work :

Set cmd.ActiveConnection = CurrentProject.Connection

Please post the table definition, sample data and I'll create the script for you...

Ya better plan >>

exec sp_update_resume

exec sp_sendBossLetter

if @@Error > 0

exec sp_distribute_resume

We'll assume it was done on purpuse (for now)... than we'll see.

How many databases do you have on the server?

When EXACTLY does it hang up in EM?

Hard to forget when you don't know about it . Thanx for the info.

Yup... but it's faster to write with xp_execresultset.

Not really any better solution here as they both have to use some sort of looping so you use whatever you preffer.

Might not be what you want to hear but :

A quote from rudy komacsar

time for:

exec sp_update_resume

and

exec sp_distribute_resume

If they don't understand the risk for that then you can't really...

This is a more evolved solution than you need but you'll get the idea :

IF object_id('Data') > 0

DROP TABLE dbo.Data

GO

IF object_id('Target') > 0

DROP TABLE dbo.Target

GO

IF object_id('Transfers') > 0

DROP TABLE...

Not quite, I'm suggesting that you alter the relationships so that when you update the parent key that all the child keys get updated without you having to do anything.

The...

Back to the original solution... please post some sample data and the expected output so that we can show you the set based solution to this problem.

Are you reffering to my suggestion??

set cmd.activeconnection = ConnnectionObject.

The timing is important too... I think that the connection must be opened when you do that or it throws another error.

Not needing a cursor is most likely true but I'm gonna state the obvious : How can you declare a cursor for update that can only read the data???

Well what??