Sergey,

Thanks for confirming that this is a bug and it has not been fixed, as well as suggesting a workaround. I tried to submit a bug report via the form you pointed me to, but I received this error:

[State=37000][Error=4064][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open user default database. Login failed.
[State=37000][Error=4064][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open user default database. Login failed.

Hopefully Microsoft will take note of both the VFP bug I hereby consider to have been reported, as well as the bug in their online bug submission form, which I also consider to have been reported.

In future, I suggest that any message whose title begins with "Bug:" should be regarded by all as an official bug report.

Mike

>I just ran a test in VFP7 SP1 with textbox on a form and it works the same: with AllowTabs = .T. tab characters doesn't trigger the InteractiveChange event. I think, you can use Keypress event (it fires before IE) in addition to InteractiveChange event to get around it.
>Anyway, I think it's a bug. You can report it here http://support.microsoft.com/default.aspx?scid=%2Fsupport%2Fvfoxpro%2Freport%2Freport%2Easp
>
>>Using VFP6 SP4, I've run into what appears to be a VFP bug. I've got an editbox with AllowTabs = .T., i.e. permitting the user to type tab characters into the control. Although this does indeed allow the entry of tab characters, it fails to trigger the InteractiveChange event, unlike the behavior for other characters.
>>
>>A quick search on UT for the past 2 years did not show any reports of such problems. I wonder if anyone can confirm the existence of this bug, and whether it has been fixed in VFP6 SP5 or VFP7. Thanks in advance for any further info.
>>
>>Mike