Subject Re: dBASE Plus 10 stops Executing
From Bruce Beacham <bbeacham@no_plm_lowman.co.uk>
Date Mon, 27 Jun 2016 23:57:48 +0100
Newsgroups dbase.getting-started

Hi

I suggest that you take the troublesome form and duplicate your code.
Then on the duplicate you should strip out all code which does not lie
in the flow which leads to the error.    Initially you should strip it
out by merely using /* ... */ to comment-out code, in case it proves
critical after all.    Keep on reducing the code and eventually you'll
be left with a small amount of code which reliably fails.    That is a
turnkey, and you should submit it to the bug-reports newsgroup.

It seems like a lot of work and at first it is, but it's quite
satisfying!    We've all done this in the past, for the greater glory.
  And it's invaluable to the R&D team, and also to you in working out a
way round the problem.


Bruce Beacham


On 26/06/2016 18:16, Norman Snowden wrote:
> dBASE Plus Executable has stopped Working
> Unexplainably now, when I try to load a particular Form I get the Message: “dBase Plus executable has stopped working” then the message: “Application caused the Program to stop working correctly.” This Form has worked fine until now and I do not know of any significant Code change that I have made in the form.
> I have another Form that is virtually the same program Code as the one that is not working. It performs a similar Calculation and still performs just fine. All my other Forms also load and work OK.
> A few times recently the Form in question did load but instead of Calculating in seconds as expected, it took about a full minute to complete.
> I rebooted the Computer and reloaded dBASE Plus 10 but this did not help. I am using Windows 10.
> If someone else has had this problem and can help I would certainly appreciate it!
> Thanks, Norman Snowden
>


Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct () in Unknown on line 0