SitePoint Sponsor |
|
User Tag List
Results 1 to 3 of 3
Thread: Client Side Objects
-
Feb 20, 2001, 07:42 #1
- Join Date
- Feb 2001
- Posts
- 9
- Mentioned
- 0 Post(s)
- Tagged
- 0 Thread(s)
I am battling to create certain client side objects within my browser (IE5) eg:
this works:
<script languange="VBScript">
set test = CreateObject("Scripting.Dictionary")
</script>
whereas this doesn't:
<script languange="VBScript">
set test = CreateObject("Scripting.FileSystemObject")
</script>
Included in the list of objects that don't work is Windows Scripting Components I have created myself.
Does anyone have any ideas or workarounds?
-
Feb 23, 2001, 18:39 #2
- Join Date
- Sep 2000
- Location
- United States
- Posts
- 1,921
- Mentioned
- 0 Post(s)
- Tagged
- 0 Thread(s)
well, if they're you're own objects, then it could always be faulty coding.
Acutally, you should also consider that you're using a specific language which generally isn't cross-browser compatible. Are you sure that your target audience uses Internet Explorer, no exceptions? Otherwise, many things that are VBScript or Windows Scripts will not work.
Just a helpful hint. As for the coding problem, I don't have many ideas on how to solve it. Sorry.
Hope this helped, however little.
-
Feb 24, 2001, 13:23 #3
- Join Date
- Jan 2001
- Location
- England
- Posts
- 338
- Mentioned
- 0 Post(s)
- Tagged
- 0 Thread(s)
I may be wrong but i thought you couldn't use file system objects on the client side as a security thing, wouldn't want people messing with files on our comps through web pages.
Server.CreateObject("Scripting.FileSystemObject") is valid on the server side tho methinks... not done ASP / VBScript for some time now.
You can't affect the local file system (client machines) in javascript.Drinky
Bookmarks