>Thanks for your reply. Actually I found a cause and a temporary solution in the registry. One of the VFP settings was -32000 for row and column. When I manually reset the values to something reasonable, the problem went away...temporarily. Apparently something on the system is re-setting those row and column settings to bogus values. >Any other thoughts? >Thanks, >Howie
Nope. Can't think of any. I doubt any non-VFP related program would change a VFP registry entry. I would check your VFP apps to see if anyone is touching it. VFP itself writes to the registry in places like the Tools/Options window.
"Once again, we come to the Holiday Season, a deeply religious time that each of us observes, in his own way, by going to the mall of his choice." -- Dave Barry
