Sean,

Actually I got your connection object example to work, needed to remove the

Server. in SET oConn = Server.CreateObject("ADODB.Connection")

So, I'll let it run for a couple of days, and see...

That's not it, Auto-Close is set to false. (One of my default settings for all DBs.)

Sean,

That didn't work at all: got the 3709 error each time.

The VBS is calling a stored procedure... There's some logic in there, and finally an insert, and yes, there is a join to another table.

But as I mentioned, it's working...

OK, that's what I thought.

I guess we're going to roll-our-own. The information management application is up for a re-write anyway, it's 15 years old, and there are plenty of things...

When you say, "Replication ALWAYS delivers data transactionally" do you mean in the same order as the changes were made in the source?

I understand that the the replication itself...

The users want some time between modifying data on the source and the mods being applied at the destination. Some changes (a typo, for example) don't need much in the...

Thanks for the input, folks.

I had come to the idea of adding a publish/go live type column to my tables, although that would involve a *ton* of work.

The time between...

It's getting SQLCMD to run that's the problem. Used to be so simple with ISQL/OSQL. Just copy the .exe, and call it.

We've got it working now using vbs to...

What isn't working is getting SQLCMD to run in the context of the user that's login in/out.

I had assumed that the policy would execute under a system/admin account.

But you're...

Still no joy.

Maybe we're going about this the wrong way.

Let me back up: A Group policy is set, and what we want to happen is

1) A user logs into domain

2)...

Yes, that's correct, they're fired by AD group policy.

So yes, I don't think the .cmds are called in the users' context. In fact, they would likely be running under a...

"...just create a desktop shortcut to the file in the prohibited folder?"

I'm sorry, I don't follow.

The logon/logoff.cmd files called by the policy are sitting on the SQL Server in...

Nope. I had apparently stumbled upon the correct control, GroupBox, but had not been able to make it work then, but it's working now...

P

Thanks Gaz, that's got it!