Hi Cetin,

Yesterday I also tried to solve this problem (adding nCurrentRecord property to the grid and to your editbox and putting go nCurrentRecord into grid.click method). Nothing helped :( The problem is (as I understand it), that we can not identify on which control we click outside the EditBox. So, I have an impression, that there is no workaround besides API functions and determination of exact place and exact control, which was clicked...

There is another problem with your editbox in a grid. Normally, I can navigate using Up/Down arrows between records. If I'm in EditMode (Grid is ReadOnly) and memo field is empty, it doesn't expand (which is good), but it doesn't allow me to navigate using KeyBoard, only mouse click.

All these problems, I'm afraid, would prevent me of using this really nice and helpful editbox in a grid. I let my colleague to make final decision here.

Thanks for your help.

BTW, multiselectgrid is another your great class, which I discovered recently and successfully used for my own purposes (see example here in UT files section).

>Hi Nadya,
>Thanks for your kind words and sorry to dissappoint you. I really tried to workaround it in a better way to no avail. I wanted to make it just drag&drop class that you wouldn't need to code something in its parent. Maybe the only workaround is totally disable left click for the control when it's in a grid. Grids are somewhat mysterious and buggy objects themselves but sure I can't live w/o them. ie: A grid textbox gotfocus fires twice, valid fire but doesn't prevent you from getting onto another control that's not part of grid, when SDI form with a colored shape is touching edge first adjacent cell than column gets colored etc etc. I checked version on my disk and yes it's the same one. Just a lockscreen and nodefault there. Lockscreen is somewhat important for grids unlike other objects :) Unfortunately I don't have a better idea now.
>Cetin
>
>>Hi Cetin,
>>
>> I tried several ways to workaround this problem, but I always had this Error message: 'Record is out of range'. Seems to be a real problem :(((((((
>>So, I think, I should leave it to be the whole Height of Width. I don't like it this way :(, because now the only way to leave this field is to hit Tab.
>>The problem is when I go outside the editbox and click, I execute click event of another control (may be grid itself, may be column, may be textbox in a column)...
>>
>> Do you think there is no workaround?
>>
>>
>>>>>>> Sorry, I have unrelated, but very important question for you: in your Expanded EditBox if I go to another field with Tab, it works fine, but if I try Mouse Click, it shows me an Error message: "Record outside the range". What should I do?
>>>>>>
>>>>>>

---

Nadya,
>>>>>>There is updated code somewhere on my disk and it's 10Gb :( I honestly even don't remember which one has the fix. I'm afraid you should wait. I'm quite busy with a brain killer project.
>>>>>>Cetin
>>>>>
>>>>>Cetin,
>>>>>
>>>>> The problem is that I already put it into our class library and into our Grid class. Sorry, I haven't tested it thoroughly. My colleague, who is a 'guardian' of our classes and who is responsible for class changes (I even have no rights to change our classes, but I did anyway) took my changes and wanted to incorporate them. She did a quick test and found this problem. Then, of course, I found it too. Actually, it may be not the problem of your classes itself. I did some code modification: where you used full Grid Height or Grid Width, I decided to use half of it and changed your code appopriately. Now I have the problem, I've described.
>>>>>
>>>>> Anyway, I can wait your update or try to investigate this problem by myself.
>>>>>
>>>>> Thanks in advance.
>>>>
>>>>

---

Nadya,
>>>>If forcing to full height&width is there than it should be the fixed version. As I remember I've added some comment about it :) And if I do remember well I couldn't find a workaround for it other than that.
>>>>Cetin
>>>
>>> Honestly, I haven't studied your code well enough, because I consider you as a very reliable source :) So, I assumed, that it should behave properly by default.
>>>But this is the code in Click() method:
>>>

>>>* relativerow=1 fix till understanding the mystery (or a bug ?)
>>>* nothing is perfect I know
>>>WITH this
>>>     if .parent.baseclass="Column"
>>>          thisform.lockscreen = .t.
>>>          nodefault
>>>          keyboard "{BACKTAB}"+"{TAB}"
>>>     endif
>>>ENDWITH

>>>
>>>Can not understand this: it locks screen and that's it? I tried to comment this code and see, if it improves situation.
>>>
>>> Is it the newest version or the old one?