Path.GetInvalidPathChars "Visual Basic 6.0 Classic" equivalent
in [Visual Basic]
|
From: Paul Clement on 12 Mar 2010 11:07 On Fri, 12 Mar 2010 09:40:41 -0500, "mayayana" <mayayana(a)nospam.invalid> wrote: � � > You could try using the VBScript Regular Expressions component with one of � the many regular � > expressions that filter invalid characters from file names: � > � > http://support.microsoft.com/kb/818802 � > http://regexlib.com/Search.aspx?k=file+name � > � � That sounds like fun. Or maybe use the � FileSystemObject's ObjFile.Name and just � trap errors. Oh wait, is this the VB group � or the VBS group? � Yeah, you're right. He should probably just dump VB 6.0, since it's obsolete anyway, and write it in a supported platform such as Visual Basic .NET. That way he can post questions in a group where he isn't berated because you can't understand his question. ;-) Paul ~~~~ Microsoft MVP (Visual Basic)
From: DanS on 12 Mar 2010 12:18 > That way he can post questions in a group where he isn't > berated because you can't understand his question. ;-) FWIW, there wasn't any confusion with what turned out to be the actual question, only the odd style of the entire post.
From: Paul Clement on 12 Mar 2010 12:53 On Fri, 12 Mar 2010 11:18:41 -0600, DanS <t.h.i.s.n.t.h.a.t(a)r.o.a.d.r.u.n.n.e.r.c.o.m> wrote: � � > That way he can post questions in a group where he isn't � > berated because you can't understand his question. ;-) � � FWIW, there wasn't any confusion with what turned out to be the � actual question, only the odd style of the entire post. I agree. It's easy enough to ask someone to clarify if there is a lack of understanding or misunderstanding, but it isn't really fair to abuse someone because of it. Paul ~~~~ Microsoft MVP (Visual Basic)
From: Jimekus on 12 Mar 2010 16:56 On Mar 13, 3:35 am, "mayayana" <mayay...(a)nospam.invalid> wrote: > > From what I found, > GetInvalidPathChars seems to just return a > [undependable] list of invalid file name characters > for the current system. > I didn't get that. I couldn't find much on it, but I first thought it returned a result using the filename as an argument. I see now where the confusion lies. I'll try the other suggested means of validating a filename. Thanks all.
From: AR88 Enthusiast on 12 Mar 2010 22:35
"Paul Clement" <UseAdddressAtEndofMessage(a)swspectrum.com> wrote in message news:ofmkp5lgr0tceurgjo31pkacr24k1nf2nf(a)4ax.com... > On Fri, 12 Mar 2010 09:40:41 -0500, "mayayana" <mayayana(a)nospam.invalid> > wrote: > > � > � > You could try using the VBScript Regular Expressions component with > one of > � the many regular > � > expressions that filter invalid characters from file names: > � > > � > http://support.microsoft.com/kb/818802 > � > http://regexlib.com/Search.aspx?k=file+name > � > > � > � That sounds like fun. Or maybe use the > � FileSystemObject's ObjFile.Name and just > � trap errors. Oh wait, is this the VB group > � or the VBS group? > � > > Yeah, you're right. He should probably just dump VB 6.0, since it's > obsolete anyway, and write it in > a supported platform such as Visual Basic .NET. > > That way he can post questions in a group where he isn't berated because > you can't understand his > question. ;-) > > > Paul > ~~~~ > Microsoft MVP (Visual Basic) Sorry Paul But I think that's absolute rubbish. Vb6 is an excellent logical product with almost infinite possibilities. Probably Microsoft's best ever. Goodness knows why Microsoft decided to dump it and inflict Vb.NET with all it's self-important C-based non-basic non-programmer friendly philospophy syntax on the community. This will go down as the most harm Microsft ever did to itself. Bill let a small number of C programmers defeat all the careful work over the years by the Vb6 developers to produce a rich language designed for the intelligent user and not some rare egghead at Microsoft. And in doing so destroyed any trust in the company. When posters here trying to unravel Vb.NET get short thrift from the Vb6 boys (and girls) it is admitedly unfortunate, but they are copping the frustration not with them but with that small number of people in Microsoft who will eventually be judged by history as Microsoft destroyers. Personally I spend half my time working to refine my Vb6 applications and the other half looking elsewhere (anywhere but Microsoft) to base my new platform on, and as far as possible to avoid any company where these Vb6 wreckers may have transferred to. |