>>>>>I don't know if this has come up before, but the SET REPROCESS TO AUTOMATIC in NewID() probably isn't the greatest idea for COM objects, since it assumes a UI to display the message.
>>>>
>>>>Curious- did this bite you, or did it just occur to you? I am glad you pointed this out...
>>>
>>> I needed to modify it for a multi-site program I'm writing and while I was going through it I realized this might cause me some problems in the future.
>>
>>With SET NOTIFY OFF, there is no attempt at UI...
>
> But then you've just added the possibility your app. will appear to lock up for no apparent reason. While this >shouldn't< normally happen, you know how things like that go ;-) With no UI to tell you what happened this might be difficult to track down. It might be better to just set it higher than you ever think it would need to be, then let it fail if it needs to. For a COM component (specifically, I'm thinking of web applications) I couldn't imagine setting it very high.
>
> As far as a specific MM change, maybe a call to IsComObject() might be in order. If it's an in-proc server, set it to maybe 10 seconds, otherwise it can stay automatic.

SET REPROCESS not only scopes to a datasession, but its settings will definitely not traverse the COM interface. It will have to be set by the COM object itself. Or maybe I misunderstood your proposal?