Re: Unicode file name

It's also disabled/removed on a lot of sites as a potential security risk
Brian. If you're distributing s/w to customers then that's a big
consideration.

Because of this, and the poor efficiency, we have an internal policy to
avoid it

Tony Proctor

"Brian Muth" <bmuth@xxxxxxxx> wrote in message
news:OUxaj4MOHHA.3544@xxxxxxxxxxxxxxxxxxxxxxx
Tony, I"ve scanned through some of these postings, and other than a few
behavioral issues (which one tends to see in any technology) I just don't
see anything that would prevent me from using FSO. We use FSO frequently
for
both scripting and VB6 and have never had issues with it in our
organization.

I think one has to be careful about posting that "such and such has bugs",
since this is how uncorroborated sentiments get generated on the internet
without foundation.

Granted, your point that FSO is not as efficient as native file support
within VB6 is valid, but I don't know if this is relevant to the OP since
he
never mentions it. There is some marginal additional overhead in
instantiating and using COM objects, but this tends to be greatly
overshadowed by the actual input/output.

Best regards,

Brian

"Tony Proctor" <tony_proctor@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:%23PI$1nMOHHA.3872@xxxxxxxxxxxxxxxxxxxxxxx
My evidence is only second hand there Brian. We avoid FSO here for all
the
other reasons I stated. However, the VB newsgroups are full of
recommendations in this area, and of scathing for FSO.

Here's a quick Google on potential bugs:

http://groups.google.ie/groups?as_q=%28fso+OR+%22file+system+object%22%29+bugs&num=10&scoring=r&hl=en&as_epq=&as_oq=&as_eq=&as_ugroup=&as_usubject=&as_uauthors=&lr=&as_drrb=q&as_qdr=&as_mind=1&as_minm=1&as_miny=1981&as_maxd=15&as_maxm=1&as_maxy=2007&safe=off

Tony Proctor

"Brian Muth" <bmuth@xxxxxxxx> wrote in message
news:Ou$PvWMOHHA.960@xxxxxxxxxxxxxxxxxxxxxxx

"Tony Proctor" <tony_proctor@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:eZQ2V$IOHHA.992@xxxxxxxxxxxxxxxxxxxxxxx
FSO is designed more for script use Brian. It offers nothing to VB
that
it
cannot do already.

True. But it is still a solution. I was really hoping it would
stimulate
the
OP to post his code, but he never did.

In fact, it's another DLL to worry about, it's big, it's
slow, and it has bugs.

I'd be grateful if you would provide me a link to those bugs.

Brian









.

Relevant Pages

  • Re: Unicode file name
    ... Tony, I"ve scanned through some of these postings, and other than a few ... see anything that would prevent me from using FSO. ... I think one has to be careful about posting that "such and such has bugs", ... Tony Proctor ...
    (microsoft.public.vb.com)
  • Re: application.filesearch
    ... It is removed in 2007 because there where a few bugs in it ... You can use Dir or FSO if you want ... in otherwords when I am typing "application." ... the "filesearch" method does not even pop up as an option.. ...
    (microsoft.public.excel.programming)
Loading