Subject Re: silent failure of the compiler From Gaetano <gaetanodd@hotmail.com> Date Fri, 18 Sep 2020 15:13:42 +1000 Newsgroups dbase.getting-started 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? Cheers, Gaetano. On 18/09/2020 14:38, Gaetano wrote: > I have a file named DATAINTEGRITY.PRG dated 15/9/2020 5:21 and a > DATAINTEGRITY.PRO dated 18/9/2020 13:09. > > For whatever reason, when I compile the file, the PRO is not overwritten > with the new version  - date and contents of the PRO are the same > without any warning or failure from the compiler. > > I tried changing the date of the PRO file to something older than the > PRG file, and made a change to the PRG file to make it more recent than > the PRO but neither of the two made a difference. > > The only solution seems to be to delete the PRO to force recompilation. > > Is this a known occasional glitch? or is it worth posting as a bug? > > Cheers, > Gaetano.