Did this article resolve your question/issue?



Getting 293 error when trying to run a .p file.


TitleGetting 293 error when trying to run a .p file.
URL NameGetting-293-error-when-trying-to-run-a-p-file
Article Number000152181
EnvironmentProduct: OpenEdge
Version: All supported versions
OS: All supported platforms
Question/Problem Description
Why would an application that runs successfully, suddenly fail with "<file-name>" was not found. (293) error?
Steps to Reproduce
Clarifying Information
Application fails after having successfully run a number of times.
Renaming of .p files in the application is occurring.
Error Message** "<file-name>" was not found. (293)
Defect/Enhancement Number
Forgetting to rename one .p file causes RUN statement calling that file to fail.
When renaming .p, .w, .i or any other files in an OpenEdge project, double and triple check that no files are forgotten. Forgetting to rename even one file can cause an application to fail.
Last Modified Date8/4/2016 12:00 PM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.