Hello, I've been using Paradox for many years, but just had a coding error that has me totally confused: I run Paradox V9 under Win 10 22H2. I had to modify some code, and on running it, was surprised to see a dialog that told me "An error was triggered in the 'Home' Method of an object of the TCursor type. This was followed by 'TCursor was not open.'" I have certainly seen this error before, but I was baffled by it in this particular situation... That's because the code did not call the "Home" Method. I had Paradox search, and the word "Home" does not appear in the code. I have relaunched Paradox, and have rebooted the System, but the odd error persists. I am eager to learn more about what might cause this to happen, and what I might do to correct the situation. Many thanks, Lothar
Try This: Check for any external libraries or components that your code might be using. Sometimes, errors can be caused by conflicts or incompatibilities with these external dependencies. Make sure they are up-to-date and compatible with your Paradox version. Review your code thoroughly to see if any hidden or indirectly called methods may be triggering the error. Sometimes, method calls can be made dynamically or through other functions, so it's worth checking for any references to the "Home" method. Look for any global variables or shared resources that could be causing the issue. If multiple parts of your code or different objects access the same cursor instance, another part of the code may be triggering the error. Consider enabling detailed error logging or debugging features in Paradox. This might provide additional information about the error, such as the stack trace or the exact location where the error is being triggered. Reviewing this information could give you more insight into the cause of the problem. If possible, try reproducing the error in a basic, isolated code snippet. By simplifying the code, you might be able to narrow down the issue and identify the precise steps that trigger the error. This might also help in creating a minimal example that you can share with Paradox support or the developer community for assistance. If none of these suggestions help resolve the error, you may need to consider reaching out to the Paradox support team or the developer community for further assistance. They might have specific insights or workarounds for this particular issue that could help you resolve it.