Hi--
How much RAM do you have? A 64-bit processor?
Check this out:
https://www.windowscentr...al-memory-on-windows-11
Also this:
https://www.tek-tips.com...ewthread.cfm?qid=296235
I think CLEAN UP INDEXES AND TEMPORARY FILES does recreate the indexes as the article describes. However, to make sure, delete all files with a .CDX extension. I just used the Windows SEARCH feature to search for *.cdx in the c:\program files (x86)\logic folder, then delete them.
Another idea--we have run into errors from a corrupt spot file. Not THAT error, but.... The way to replace it would be to delete logdata\spots.cdx then reinstall the latest update. But I attached my copy to this post. Just unzip and save it to the logdata folder. I did not include spots.cdx, so do a CLEAN UP INDEXES AND TEMPORARY FILES or delete all indexes manually.
Do you keep your spots around forever? PERHAPS a large spot log file MIGHT do it. With VFP10, I doubt it. Regardless, replacing the spots file will take care of that possibility.
The article also mentions "very deep classes." Not sure what they mean by that, but will research it.
Also, it wouldn't hurt to temporarily disable any antivirus program. I just use Windows Defender or whatever comes with Windows 11. I also run the free version of MalWareBytes -- it does not run in the background. I just run it when I suspect a problem -- it sometimes finds stuff that Defender misses. But I haven't had problems in a long time -- I don't think I have run it on Win 11 ever.
We have narrowed the problem down to a combination of the spot log and telnet. Try taking telnet out of the picture and use DX-Summit.
Tnx/73,
Dennis WN4AZY