>However, do you really think the issue that George brings up as being all that complex???? Cmon, it is a basic API question. If that is too complex for the TE's, I would recommend getting new TE's...
>

There is an issue here, clearly; that the editorial staff did not have the presense of mind to at least try the tip under 9x, NT and 2K before publishing the tip is the issue. The technical capabilities to deal with this are there in the nominal CE community for FPA; Christof's there, and if no one else on the staff had his level of detailed background on the API, if the tip were tested and something broke, then he could've been asked and would've spotted it in a heartbeat, because he knows the issues as well as any of the API-capable people here.

That someone might miss the issue on a casual read-through would be a simple matter of a cow flew by and he missed it. That the editors couldn't be bothered to check to see that their facts were straight is another matter entirely. George, or you, or I, or any individual might miss a fine point on a bad day. That's why there's a review before publishing something.

Or at least there should be.

I think the point here is not that any individual editor at FPA should be fish-slapped for this. The editorial staff of FPA is at fault, and it's a failure to manage the process of getting quality material to print that's at issue. There's review of material at other magazines; Doug Hennig checked with me about one of my files before he referenced it for a column in FoxTalk, and he'd tested to make sure that what he wrote about in his column was valid and correct and current. I haven't seen this kind of glaring mistake in something from FoxTalk in ages, and I read it in detail. Every issue.

I think the best indication I have that I don't pay much attention to FPA is that the magazine had been in the house for several days and I hadn't pulled the plastic wrap off of it when George sent me email to confirm that NT did have a known issue with DISKSPACE(), and he'd already let me have both barrels of rock salt in the butt for thinking he'd forgotten about SetErrorMode() before I even bothered to look at FPA. I'd been up at Pinnacle's site to grab FoxTalk a few minutes after Mike Helland let me know his article had been released there.

FWIW, I am not unbiased here. I like the FoxTalk format, and see FPA as a far less important resource for me. But I don't have an axe to grind with FPA other than (1) the content is not targeted at my market segment, and (2) the recent work product has been sloppy.

What I've said here is my opinion. The only weight they need to give to the statements above are that as a paying customer, I'm not pleased with the quality of product I'm receiving from them. The best reply that could be made to this would not be a detailed apology from their staff. The best reply would be to fix what's wrong so that this kind of avoidable mistake doesn't happen.