--
Dim Alan as ThatsIT.net.au.Staffmember
Alan.signature = "Thank You"
Response.Write Alan.signature.toString()
__________________________________________
"Anthony Jones" <> wrote in message
news:...
>
> "ThatsIT.net.au" <me@thatsit> wrote in message
> news:...
>>
>>
>> --
>> Dim Alan as ThatsIT.net.au.Staffmember
>> Alan.signature = "Thank You"
>> Response.Write Alan.signature.toString()
>> __________________________________________
>>
>> "Bob Barrows [MVP]" <> wrote in message
>> news:...
>> > ThatsIT.net.au wrote:
>> >>> Dim objFSO: Set objFSO=CreateObject("Scripting.FileSystemObject")
>> >>
>> >> try Server.CreateObject("Scripting.FileSystemObject")
>> >> not
>> >> CreateObject("Scripting.FileSystemObject")
>> >>
>> > Why? That's neither relevant nor necessary.
>>
>>
>> You are probably right, but I know there are some objects you must use it
>> on,
>
> Oh that's interesting. Which ones?
>
I don't remember, that why I always use it.
wait I have found the article where I read it
http://classicasp.aspfaq.com/compone...ateobject.html
also it points out if you are using JavaScript you must use
server.createobject
I don't use JavaScript and I don't use any third party objects I can think
of either.
like I said I use it just in case, although the article also points out a
overhead, I have never found it to be a problem.