It seems, Alan, that Microsoft (and so everyone else, MS being the leader) is still using the limitations of a "paper world" when it comes to documentation even though they haven't distributd paper documentation for years.
You would think that by now they would see the sense/value in REPEATING important notes WHEREVER they might apply. In a paper world this can be tough and costly, but it should be sooooo easy in the electronic media now in use.
They also STILL think that putting only the type of the value returned under "RETURNS" is good enough. Like it's real hard to put, right where it belongs (i.e. not way deep in the remarks).
They also STILL think that burying default values within the parameter's description is fine (or even in Remarks in some cases) when the clear logical USEFUL place for it is right in the heading for the parameter, beside the paramter syntax line itself.
It sure looks like Microsoft is actually giving up on documentation generally, letting other people do the job for them! .NET seems rife with (very specific) "good" documentation on non-MS sites while MS' own .NET documentation remains the butt of jokes. Major .NET 'magazines'. including MSDN's own, seem to all need a "Doc detective" or similar column. SAD!!!!
>Yes, Sergey said the same in a message to somebody else. Still, I think it should say so in the 'Set Seconds' topic ('Set Hours' too). In any topic, if there is an exception, then it should say so
in the topic.
>
>>>Fabio, I don't see anything in the help file that says it doesn't work with
SET DATE SHORT or
SET DATE LONG, so why isn't it a bug (at least a bug in the help file).
>>>
>>Alan, it is a Documentation issue ( it is normal ).
>>I read :
>>SHORT
>> Short date
time format determined by the Windows Control Panel short date
time setting.
>>
>>
>>SET HOURS TO has the same behaviour.
>>
>>
>>SET DATE TO SHORT
>>SET HOURS TO 24
>>SET SECONDS ON
>>
>>CLEAR
>>? DATETIME( )
>>SET HOURS TO 12
>>SET SECONDS OFF
>>
>>? DATETIME( )
>>
>>
>>Fabio