Kbase 18053: Filename Not Found (293) When Importing Data
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Verified
FACT(s) (Environment):
Windows 32 Intel
Windows NT 32 Intel/Windows 2000
Progress 8.x
Progress 9.x
SYMPTOM(s):
** "<file-name>" was not found. (293)
Problem importing data.
xxxxxx.adm Was Not Found (293) When Importing Data
CAUSE:
This always indicates a problem with the PATH.
The PATH environment variable did not contain an entry pointing to the Progress BIN directory (C:\Progra~1\Progress\Bin).
FIX:
To import data, Progress uses an MS-DOS program called QUOTER.EXE. This program does not look in the PROGRESS.INI file or in the Windows Registry for environment variables. Setting PATH= in the PROGRESS.INI file will satisfy most requirements but does not work for QUOTER.EXE.
If QUOTER or the database import option is being used, the PATH must be set at the operating system level.
In Windows 3.1, Windows 95, Windows 98 and Windows Me, add the following line to the AUTOEXEC.BAT file:
V8 example => PATH=C:\DLC\BIN;%PATH%
V9 example => PATH=C:\Program Files\Progress\Bin;%PATH%
Be sure to substitute the appropriate subdirectory in place of "C:\DLC\BIN" or "C:\Program Files\Progress\Bin" in the above examples if your Progress home directory is different.
In Windows NT and Windows 2000 go to the Control Panel, select SYSTEM, select ENVIRONMENT, then add the following to the System PATH variable:
V8 example => C:\DLC\BIN
V9 example => C:\Program Files\Progress\Bin
Once again, be sure to substitute the appropriate subdirectory in place of "C:\DLC\BIN" or "C:\Program Files\Progress\Bin" in the above examples if your Progress home directory is different.
IMPORTANT: Do not replace the existing PATH variable on Windows NT or
Windows 2000, simply add to the existing PATH.