> I've heard strong arguments both ways. One the one hand, in ASP pages,
> the $Server->CreateObject() method is already available without needing
> to be 'use'd or imported or the like; saves on startup. OTOH,
> Win32::OLE is a more portable solution since it's available in most
> Win32 installations of Perl, and doesn't require the ASP object model.
I've solved that by making all my database functions require a reference
to a Connection object to be passed into them, use a local recordset to
do stuff, and return things via a reference to a hash so my funtionality
is the same outside of ASP.
$conn = $Server->CreateObject("ADODB.Connection");
$Reponse->Write( ref $conn );
tells me that its a Win32::OLE object. So including Win32::OLE shouldn't
hurt anything as its only including once.
Connection pooling shouldn't be an issue either becuase that's done at
the level of ADO.
I stick to ther $Server method in case I want to send the connection
object to a VBScript sub.
_______________________________________________
Perl-Win32-Web mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-web
