JK..

Then the space the former editor occupied was for what purpose????
The the space the current technical editor occupies is for what purpose???

This is what the editor is for. Specifcally, this is what Tamar's job was. And, Tamar did have control over the April Issue.

TE's will work with the managing editor in this capacity now. Of course, with Tamar still on board as a TE, it begs the question of whether things will get better.

Notice I have not mentioned contributing editors. Their role is symbolic. More bluntly, CE's don't do squat with respect to editing articles... They may get solicited for advice from time to time with general editorial issue, but that is about it.

The bottom line is, if you pay outsiders to spot check articles, why the hell do you need Technical Editors????

>
I don't know if this is practical or not, but can't Advisor pay someone externalk a few bucks to spot check articles and tips before they are published? I have been asked by other publications to do this when an article was going to be published that mentioned VFP.
>







>
>>You should send this to the following address:
>>
>>foxpro@advisor.com
>>
>>Thanks for posting this... If more folks do this, maybe FPA will start to listen.
>>
>>>In light of or more of the recent threads in this area, here's a little something from the "Advisor Tips" section of FPA. As a side note, I find it interesting that Steve Sawyer is no longer the editor of this column.
>>>
>>>The title of this gem is "Determine if a Drive Exists". Without getting into any of the text, it has the following RETURN:

RETURN (DISKSPACE(tcDrive) > 0)

where tcDrive is the drive in question.
>>>
>>>Only one problem...under NT you get a nasty error dialog if SetErrorMode() isn't properly called (and later restored to it's original state) to disable it.
>>>
>>>Now if you're going to be mucking about with API anyway, then...

DECLARE INTEGER GetLogicalDrives IN Win32API
>>>RETURN BITTEST(GetLogicalDrives(), ASC(UPPER(tcDrive)) - 65)

>>>
>>>gets the job done very cleanly.
>>>
>>>Back in the January, 2000 issue, while Steve was still the Contributing Editor, there was a tip that synchronized the VFP _DBLCLICK system variable with the setting the user had established in the Control Panel:

DECLARE INTEGER GetDoubleClickTime IN Win32API
>>>_DBLCLICK = GetDoubleClickTime() / 1000