Hi Jim -

It might get even more 'interesting'.... :)

The two systems are as follows:
P200 Pro w/32Mb RAM - Running W98
vs.
P166 w/32Mb RAM, then we upgraded to 64Mb RAM - Running W95
(There didn't seem to be any significant difference between the 32Mb and 64Mb with this problem.)

There is no code in the interactive change anywhere up the line and it is only 1 level deep. (ie. the textbox on my form is based on a subclass of the original VFP textbox).

I will have to do some other tests to try to track down what exactly is causing this, but for the next few weeks I am going to have to stay in VFP5. The next version of my app is due shortly, and I don't have time to research/re-test it in VFP6. Hopefully, someone will have some ideas .....

TIA -
ellen

>What is your operating system. If you're running 95/98, 64 Mb of memory should be sufficient, but w/ NT 4.0 it's barely adequate. You say there's no code in the InteractiveChange. Is this true up the Lineage-line? Is there any difference between a TextBox based on VFPs class and one 3-4 levels of inheritance deep?
>
>I've noticed problems w/ MMX chips regarding display. Is there any difference between your 166 and 200 in any regard besides speed rating? ie: one is a knockoff...
>
>It sounds like an "Interesting Phenomenon". That means it's happening on your machine. If it was happening on _my_ machine it would be a "Big Damn Problem"!
>
>jt
>
>>On my app(that I converted from VFP5) on a P166, w/64M RAM, just tabbing thru the controls is slow (even tho it's not hitting any code). It is also sluggish when I enter data in a text box. In fact, I can get 3 or 4 letters ahead of seeing them appear on the screen(no code in the interactiveChange)! Neither of these things happen on my P200.