Automatic PRJ generation
QV2QS can generate missing PRJ folders automatically before starting a batch conversion, removing the need to create PRJ artifacts manually for each source file.
QVW and QVF files require a PRJ folder for conversion. If the scanner finds source files without matching PRJ folders, QV2QS can generate the PRJ folders automatically before proceeding with the batch.
Enable automatic PRJ generation with --generatePrj on the command line or the Auto-generate PRJ toggle in the user interface. QV2QS uses the bundled QlikView Desktop engine to extract each source file into a PRJ folder, then re-scans the directories to pick up the newly created folders.
In batch mode, QV2QS generates PRJ folders only for source files that do not already have a matching PRJ folder. Existing PRJ folders are not regenerated. To force regeneration for a specific file, delete the existing PRJ folder and re-run the batch. Alternatively, open the QVW file in QlikView Desktop and save it to regenerate the PRJ folder in place. In single-project mode, --generatePrj always replaces the existing PRJ folder.
PRJ generation runs sequentially (one file at a time) because QlikView Desktop can only process one file at a time. Each file is processed in a separate subprocess to prevent conflicts. The timeout is 10 minutes per file and is not configurable. If another QlikView process is already running, PRJ generation fails with a conflict error and cancels remaining files. Close any running QlikView instances before starting batch conversion.
PRJ generation failures do not abort the batch. Files that fail to generate a PRJ folder are skipped during the subsequent conversion. The scan results report which files were skipped.
In the user interface, the Generate Missing PRJs button in the scan modal generates PRJ folders for selected files on demand. Progress updates appear in real time. Only one PRJ generation job can run at a time.
Diagnosing PRJ generation failures
If PRJ generation fails, check the system log at %LOCALAPPDATA%\QV2QS\qv2qs.log. Search for No QlikView Desktop found, Batch PRJ prerequisites, or the source file name to locate the relevant entries. Run with --logLevel DEBUG for detailed logging. For more information, see QlikView Desktop issues and Logging and diagnostics.