I cannot give you the contents of the error log since it contains nothing.  QB64 gives me the option to click on the error to go to the error log but it is always blank.  That leaves me with no where to go. A real dead end.  Where do I start to find my problem in a couple thousand lines of code?

And why will code that failed to compile in one instance of QB64 compile in a different instance of QB64 (until a save)?  I have demonstrated this to my self several times.  In spite of this baffling issue, I do like QB64.

Darrell




















qb64.  I have

Hi
My first post. 
I copied your code into QB64 Version 1.4 in a Linux Mint 19.3 ThinkPad E550 laptop.
It compiled just fine.
Hope that is of some benefit to you.

After the successful compile, I got a black screen with this prompt:  starting record? and a blinking cursor.

I have had my own problems with Compile failure.  I converted a fairly complex program I wrote some years ago in QB 4.5 into QB64.  At first it compiled OK. As I continued to modify the app, it suddenly would not compile.  QB64's error message invited me to check a log file that was non-existent (completely empty) .

Here is the strange part:  I have several examples of QB64 on my three computers.  If I load my app into a different copy of QB64, (even on the same computer) the app will compile OK!  That is, until I save it.  I can even do some simple adjustments to the app and it will continue to compile until I perform a 'Save', then the same compile error and empty error log.  Once I get the compile error, no future efforts to compile that app is successful.  Other apps will compile just fine, though.
This problem is what brought me to this thread.

Anybody have a clue as to what is going on here?
What can I do to finish my app (which I really would like to use)?
Darrell Bosely