I've had this annoyance for years...but it recently got really bad.

When I have a code window open (like for a form method) and I highlight a word or string of word in the program code, as soon as I CTRL+C or click the copy icon on the toolbar, VFP goes to lunch..."Not Responding"...window goes white-ish.

If I let it sit, long enough (like up to 5 minutes), it will eventually recover...until I commit the same mistake of trying to copy text to the clipboard. (Which I do in order to search for other occurrences, etc.)

I had this trouble in the past and I finally decided to try the NUKE solution and deleted the FOXUSER.DBF file.
BOING! Fixed that problem! Copy works like a big dog on steriods now!
Unfortunately, it also dumped all of the other 3000+ settings and things VFP keeps track of for reuse later. Things like smartcomplete where you type "do<space>" and it pops up a list of all the programs you've recently run...which I depend on a lot!

After a while, that good stuff builds back up and things are good again, but the COPY to clipboard seems to be even worse now (freezing for even longer periods.)

So, my question: Is there a way, like PACKing or deleting a certain row in the FOXUSER file, to get the COPY to clipboard to work as it should but without loosing all the good stuff VFP remembers? (like projects recently worked on, etc.)

Thanks for any guidance...heck I'll even take a LMGTFY or three if it helps!

Mike Copeland

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to