>George, why exactly would the fact that _cliptext is limited to text be a problem? Wouldn't _Cliptext = "" clear the clipboard regardless what might be on it at the moment? I've been clearing it that way myself, but if there is a problem coming down the track that just hasn't run me over yet, I'd really like to know about it.
>>
>>Wait a second. I just thought of something. Is it because maybe I'm not really clearing it, but actually setting it to an empty string? Could that be an issue?
>>
>Alan,
>
>As Anatoliy explained, the clipboard isn't limited to just text. It supports an number of different formats. So while setting _CLIPTEXT to an empty string may remove any text available to VFP, it doesn't remove the other formats.


When anything is put on the clipboard, it replaces whatever was there before, no? If I have a bmp in the clipboard, and I do '_cliptext = ""', the bmp is gone. All that is left is an empty string, so it appears that it really does remove other formats.

Having said that though, I understand now about the clipboard handles. An empty string needs handles. True 'emptying' of the clipboard releases all handles.

Thanks

Alan

As with so many other things in programming, it all depends on the definition of what >"emptying the clipboard" is. If it's simply removing the text for the current application, then, yes, setting the system variable to an empty string is the solution. Otherwise, no, it isn't. How we define problems ultimately leads to how we define what the solution is.
>
>Regards,