Project "Build Time" Text Error File Missing 1

[HDS]

During the Build of a application from a Project any errors encountered are normally logged in a text file named with the project name and a '.err' extension (i.e. project1.err). I have used these text file error logs many times in the past. However, during the build of my current project I received a dialog box indicating a file or directory could not be found (not very helpful). When I looked for the error log to get more information (i.e. which file could not be found), I could not find it. I have searched the entire disk with Explorer's Search and it does not exist anywhere on the disk.
I have found only one option relative to the error log. It is located on the build menu and it allows automatic display of the error log at the end of the build. I have switched that option on, but still no error log.
Any ideas as to why I'm not getting the .err text file?

 

[jworley]

I've had this before, and the only 3 ways I could resolve the problem were to:

a. Remove the database from the project, save the project, add it back in and validate.

b. Try building again, if it doesn't work then remove all forms, programs, classes and other items from the project and add them back in one by one.

c. If all of the above fails, create a new project and add all your forms etc. back into it.

I've also heard that this can happen when a class contains an object that no longer exists, although I've never had that problem.

Jim Worley
jim@aits-uk.net

http://www.aits-uk.net

15 years practical IT experience from sales to support to development plus B.Sc. (Hons) Computer Studies, fluent German speaker, willing to have a go at anything and don't suffer fools gladly !

 

[HDS]

Jim, Thanks for the post!
Lady Luck has smiled on me since I posted the question.
As the build executes, file names are displayed on the status bar, but too fast to read. I entered the following command in the command window, hoping to get a more useful error message: ON ERROR ? SYS(2018) I then ran the build again. When the build hit the error, it hesitated a couple of seconds, giving me just enough time to read the current file name on the status bar. The missing file (procedure B) was a procedure called by procedure A. Procedure A had been added to the project but Procedure B had not been added to the project. After I added Procedure B to the project the build completed successfully. Curiosity then got the better of me, so I intentionally put a coding error in another procedure in the project. Ran the build and sure enough the build created the error text file just like it is supposed to... Looks like the builder has a bug.