From: Metre Meter on 8 Jan 2010 18:42 On Jan 8, 2:17 am, "Bob Barrows" <reb01...(a)NOyahoo.SPAMcom> wrote: > Metre Meter wrote: > > But the methods I can call on the Server.CreateObject created objects > > are those of the same ADO COM object created by any other machines > > (barring security considerations), right? > > Other machines? I've no idea why I typed "machines", because it's certainly not what I meant(!) I'm pretty sure that it should have read by any other means". > No, it can only access activex dlls that are installed > (registered) on the machine on which the script is running. That's very informative, thanks. So I can create all sorts of COM objects, so long as they've been registered with the server? - MM
From: Bob Barrows on 8 Jan 2010 18:57
Metre Meter wrote: > On Jan 8, 2:17 am, "Bob Barrows" <reb01...(a)NOyahoo.SPAMcom> wrote: >> Metre Meter wrote: >>> But the methods I can call on the Server.CreateObject created >>> objects are those of the same ADO COM object created by any other >>> machines (barring security considerations), right? >> >> Other machines? > > I've no idea why I typed "machines", because it's certainly not what I > meant(!) I'm pretty sure that it should have read by any other means". > >> No, it can only access activex dlls that are installed >> (registered) on the machine on which the script is running. > > That's very informative, thanks. So I can create all sorts of COM > objects, so long as they've been registered with the server? > Exactly. -- Microsoft MVP - ASP/ASP.NET - 2004-2007 Please reply to the newsgroup. This email account is my spam trap so I don't check it very often. If you must reply off-line, then remove the "NO SPAM" |