Current concensus on using WSH libraries from Access

[Steve Jorgensen]

I've been following a policy of avoiding any libraries that come from the WSH
since some system admins (including me when I was part-time sysadmin) wouldn't
allow them on their systems.

Since then, MS has clamped down harder on security in that area, and there is
more and more code in the world that assumes these libraries will exist. If,
for instance, you want to stream to a file from SAX in MSXML from VB/VBA, the
FSO from WSH is the -only- way to do it.

So, at this point, it it becoming OK to make use of the WSH-provided libraries
for the very handy dictionaries and file system objects? Also Are they
tending to break or preserver binary compatability in WSH over time (in
contrast to, say, the common controls library)?

[Rick Brandt]

Steve Jorgensen wrote:

I've been following a policy of avoiding any libraries that come from
the WSH since some system admins (including me when I was part-time
sysadmin) wouldn't allow them on their systems.

Since then, MS has clamped down harder on security in that area, and
there is more and more code in the world that assumes these libraries
will exist. If, for instance, you want to stream to a file from SAX
in MSXML from VB/VBA, the FSO from WSH is the -only- way to do it.

So, at this point, it it becoming OK to make use of the WSH-provided
libraries for the very handy dictionaries and file system objects?
Also Are they tending to break or preserver binary compatability in
WSH over time (in contrast to, say, the common controls library)?

I still have never used it, but I am interested in your SAX comment. I use the
MSXML library to do SAX parsing and for HTTP Requests and have never had to use
the WSH. What exactly do you mean "...stream to a file..."?

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[Steve Jorgensen]

On Fri, 26 Aug 2005 11:29:50 GMT, "Rick Brandt" <ri*********@hotmail.com>
wrote:

Steve Jorgensen wrote:

I've been following a policy of avoiding any libraries that come from
the WSH since some system admins (including me when I was part-time
sysadmin) wouldn't allow them on their systems.

Since then, MS has clamped down harder on security in that area, and
there is more and more code in the world that assumes these libraries
will exist. If, for instance, you want to stream to a file from SAX
in MSXML from VB/VBA, the FSO from WSH is the -only- way to do it.

So, at this point, it it becoming OK to make use of the WSH-provided
libraries for the very handy dictionaries and file system objects?
Also Are they tending to break or preserver binary compatability in
WSH over time (in contrast to, say, the common controls library)?

I still have never used it, but I am interested in your SAX comment. I use the
MSXML library to do SAX parsing and for HTTP Requests and have never had to use
the WSH. What exactly do you mean "...stream to a file..."?

If you want to use SAX to stream output directly to a file on disk, the only
IStream object I can find of that can do the job is in the FSO. If you want
to do it indirectly, you can output to an ADO Stream, then save that stream to
disk afterward, but that kinda defeats the point of SAX.