Subject Re: silent failure of the compiler From Ken Mayer <dbase@nospam.goldenstag.net> Date Fri, 18 Sep 2020 06:12:28 -0700 Newsgroups dbase.getting-started On 9/17/2020 10:13 PM, Gaetano wrote: > > OK, so deleting the PRO forced recompilation of the PRG, but I still had > the same error ( I thought I had landed in virus territory), so I > checked the target folder of the executable and there was a > DATAINTEGRITY.PRO file in that folder and it seems that dBase was using > that external PRO file instead of what was included in the executable. > Once I deleted that obsolete PRO, the one in the executable got used and > the program completed successfully. > > Does the EXE first look externally for required objects? Has this always > been the case or is it something introduced with DEO? In Chapter 26 of The dBASE Book, I put together the sequence (based on conversations with the folk at dBASE) that dBASE itself looks for the necessary files. 1) It looks in the folder with the .exe (the home folder) for the object (.pro, etc.), if found it executes the object file and stops looking. 2) If it does not find it in the home folder, it looks in the .ini file for the DEO object path entries -- if found, it executes the object file and stops looking. 3) It looks internally -- in the .exe to find the compiled object and if found, executes it. If not found, an error occurs, telling you (or your user) that the object file cannot be found. It helps to understand how this works ... Ken -- *Ken Mayer* Ken's dBASE Page: http://www.goldenstag.net/dbase The dUFLP: http://www.goldenstag.net/dbase/index.htm#duflp dBASE Books: http://www.goldenstag.net/dbase/Books/dBASEBooks.htm dBASE Tutorial: http://www.goldenstag.net/dbase/Tutorial/00_Preface.htm