>So make the changes and submit it as a new FAQ......help yourself.

Why it should be a new one, if yours already covers it? There is an Update button, and you can just mention this, so it would save some time for users, who take it literally without adjustments...

Thanks in advance.

>
>>An offtopic, but could you please be a little more specific in your FAQ about canceling validation. You should mention, that if Cancel button is in some container, we need to calculate top, left positions relative to the form, not to the parent. Took me some time, before I figured this out and adjusted your code example appropriatelly. Once I did, it worked great.
>>
>>>(Sorry I didn't see this sooner)
>>>
>>>Yes, the "magic" number is based on the band being 19 pixels in height. When I wrote the article, I had forgotten exactly where I got the number from ... so I omitted the explanation (which I guess was a douchebag thing to do - lol)
>>>
>>>I invite Denis to download my FRX2Word class here and see how I go through the VPOS and HPOS and decode them. You know that phrase about a picture being worth a thousand words? In this case, code is worth a 1000 words :-)
>>>
>>>
>>>>
>>>>>But, what are you thinking about "magic constant" 1979.16666666
>>>>
>>>>This value isn't exactly "magic". Here's the logic: there are 10,000 "report units" per inch and 96 pixels per inch. The height of the band separator is 19 pixels. So, 10000/96 = 104.166 and 19 * 104.166 is 1979.166. My logic of 2083.333 was flawed, because that measures to the bottom of an object that's 104.166 report units high, not to the top.
>>>>
>>>>Doug