>>Hi. I'm hoping someone can shed some light on this. We have a computer running Win 95 (with all patches), 72 MB RAM - it's a laptop, and another group of machines running Win NT Workstation Service Pack 4. On all these machines, we get a Internal Consistency error when we perform a series of keystrokes in our application. The problem cannot be reproduced on machines running WIN 98 SE, in either runtime or development. The Win 98 SE machines (3) are different makes with different video cards, different amounts of RAM, etc. All the machines have tested this keystroke with the same EXE and same data...
>>
>>I can't find anything specific about this. The keystrokes involve one screen (SCX) where you add a record, add one item through a browse, save the record using F10, ESC the screen and then go to another screen that displays the screen. THe second screen contains only one field on it (as it is a report generator screen) and it gets the error as soon as the screen comes up. There isn't anything unusual about the coding of either screen, as the rest of the app is coded similarily.
>>
>>TIA
>>
>>Sandi Cassidy.
>
>
>Start with the KB article on my web site. If that doesn't help, come back here and post a followup message.

We did everything in the KB article (and a bit more) and still cannot solve this. Could it be related to some component of Windows that affected memory management? Since it happens on more than one computer, but not all computers and it happens with exactly the same dataset vs not happening and only with this screen and this keystroke combo, I am stimied. The only unusual thing on this screen (compared to other screens in the app) is that within the browse window, one of the fields is a memo field, which has a When clause that causes an edit box to open so you can enter the value. When not in the field, it shows the first 24 characters of the memo field.
Any other ideas?

TIA

Sandi Cassidy