Re: Mass delete files and directories

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Actually, size-wise, Boolean is equivalent to Integer in VB.

Strangely, all VB samples I can find have that field as Long, so I'm honestly not sure why I have it as Boolean myself! But it was worth a shot, anyway. Like you, I remember stumbling across a problem a long time ago relating to one particular OS, but it's so far gone that I don't remember the what & why of it. The fact that I have the one field declared as a Boolean when everything else says it should be Long, though, made me suspicious that that might be the case.


Rob

Grand_Poobah wrote:
I checked with the MSDN site and the API reader before I inserted the code into my program. The definition is Boolean instead of Long. Size-wise it makes no difference, but Type-wise is probably does.

A short test program to all four testers produced a Copy, Move, and Delete on three machines, and three failures on the one machine. I am beginning to wonder if maybe the OS on his machine might be something like Win2K or W98 with a strange version of the "shell32" library. In all three failures, the source file was not moved or deleted which would indicate that the API call blew out.

GP
.

Relevant Pages

  • Re: [PATCH] mtrr use type bool
    ... This seems a bit strange, using a boolean as an integer. ... if (increment) ... many places had/have some sort of a = b? ...
    (Linux-Kernel)
  • Re: EDatabaseError possible Delphi bug???
    ... That should have read "Cannot access field 'xxx' as integer." ... > I am getting a really strange EDataBaseError..."Cannot access filed xxx as ... > in the Access database: ... > zzz boolean ...
    (borland.public.delphi.database.ado)
  • EDatabaseError possible Delphi bug???
    ... in the Access database: ... zzz boolean ... the really strange thing is that I can READ xxx asboolean, ... Rgds ...
    (borland.public.delphi.database.ado)
  • Re: Passing arguments to function - (The fundamentals are confusing me)
    ... Sharing an arbitrary boolean, without any context, is rather strange -- perhaps it would be best to include both the boolean and associated context in a single, larger object. ...
    (comp.lang.python)