Fabio,

>I can proof it easy;
>in fact the proof is within to your BuildAnchor form,
>watches it with attention and perhaps you will see it.

That is no proof at all, either give two concrete examples or just drop it. There is no way to represent 10 bits of data with 8 bits of storage.

>However I have inasmuch as Aleksey is not interested to improve the Anchor
>(can be improved of 10000% with little hours of C++ programming)
>and therefore argument without practical scope is useless to open one.

10000% is quite a change for only dropping 2 bits.

The relative positioning in your other thread shows what amounts to quibbling over a few pixels. If I expand that form to full width of my display the textboxes expand from 150 to 916 pixels and the space between the two columns expands from 10 to 56 pixels. It's pretty hard to justify a complete change so that the textboxes would be 939 (916 + (56-10)/2) pixels. You'd probably get a comment from a graphics designer that the additional white space is a good thing. If those pixels are that critical to your form you can always still use your own custom resizing code. There's an article on my website that shows how you can write your own C++ DLL and call it from VFP, so a couple of hours of your time in the C++ compiler and you'll have your own perfect solution.

In this thread you are saying there are too many complex bits to manage and in the other thread you are advocating the addition of 4 more bits.