All generic functions go there while all program specific ones are in the same directory as main.PRG. There I have dozens of UDFs, PRGs, etc grouped in different directories by what they do. The problem lies, I think, in the Library function directory. I am assuming that I will have to include the full path for FP to find them. FP cannot find the files - I have to manually remember where they are at. When I include those xxxx files as EXTERNAL PROCEDURE xxxx.PRG, things do not change. In my main.PRG and tried to build a new instance of my project under a different name, I get multiple 'Unable to find Unknown xxxx' errors where xxxx is the name of some function, procedure, or whatever. Seems that the problem lies in my organization of Library functions. Still having problems implementing your suggestion. RE: Corruption of PJX file mmerlinn (Programmer) "Political correctness is the BADGE of a COWARD!" Unfortunately, added/modified/deleted files in the corrupted PJX file are not in the saved file, so it sometimes takes me hours to bring the saved PJX file up to speed and working properly before I can pick up where I left off in the developement of the app. Then when I need to recover, reload the saved PJX and PJT files, and use them as the base to continue building the app. Either way, when that happens, it takes me a long time to get the PJX file working again.ġ) Is there any way, short of trying to remember to close the PJX window after every build, to automatically circumvent this problem? Closing the PJX window dozens of times per day and reopening it every time to modify the app is a royal pain, and is easily forgotten at the worst possible times.Ģ) If not, is there any simple way of recovering from corruptions that will sooner or later occur?Ĭurrently, I periodically save the whole project, including the PJX file to another disk. And when there is an error in the app, the PJX file either doesn't get saved with the modifications, or it is getting saved with corrupted modifications. Obviously, the PJX file is being corrupted because the modified PJX file is not being saved until the PJX window is closed. And never when the PJX window is already closed. This happens only if there is some sort of an error in the application, never when the app runs correctly. PJX window after building the application and before testing the application the. And I just today got hit again, fortunately for the first time in months.ĭuring developement using FP2.6, if I fail to immediately close the. This has been an ongoing problem for me for years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |