Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Crashing VFP from error handler
Message
From
17/12/2021 06:34:45
 
 
To
16/12/2021 16:59:28
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Miscellaneous
Thread ID:
01682978
Message ID:
01682987
Views:
63
Thanks for all the ideas.

>1. If you have non-Microsoft antivirus, try disabling its real-time scanning component
>

Just Microsoft antivirus and in trying to resolve this, I excluded the folder containing this table. No help.

>2. Is your Errorlog table a conventional local file on conventional local storage, or something else e.g.

On a local drive, though it's a mapped drive name.

>- Cloud-synced storage such as OneDrive or a SharePoint Online document library? If so you could try temporarily disabling sync for those files

Nope.

>- Is Windows 10 File History or any 3rd-party real-time/cloud backup software running?

File History is turned off. No real-time backup software.

>- On a file server or NAS?

Nope.



>3. (you might want to try this first) Do you have another computer from which you can run your tests - to see if it's something in one particular computer or in your environment

Not easily, but will if I have to. Just a complicated set-up for this application. The fact that other users aren't running into this does seem like it's something particular to my setup.


>- are you testing on a physical computer or a VM?

Physical computer, though a mapped drive.


>4. Are you actually running low on free space on *any* drive connected to your test machine? Do you have compression turned on for any drive in question - if so it's a good idea to be conservative about free space. For example, one rule of thumb for uncompressed drives is 15% free is yellow alert, 10% free is orange alert, 5% free is red alert. As a very rough rule of thumb you can double those values for compressed volumes

No. Got three drives, each around 1TB, each with 785 or more GB free. That's actually two physical drives, one a SSD C drive with Windows, etc. installed, and one conventional drive partitioned into two for D and E.

>Update:
>
>5. Maybe your ErrorLog table has subtle corruption (like a CHR( 0 ) in a memo or char column), or an index tag corruption

But deleting and recreating the table should have resolved anything like that.

Tamar
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform