File Extensions
On this page
8.3 File Extensions
Show full extensions in Explorer. Suffixes suggest purpose but do not prove authenticity/completeness or convert formats.
8.3.1 Layouts, Synchronization, and Reports
| File | Purpose | Boundary |
|---|---|---|
.skdCard |
Saved CDPS design/configuration for COC | Not a personnel database or full external-resource backup. |
LayoutDefinition.clcf |
Synchronization connection/settings | Not an editable ordinary card or complete deployment package. |
.repx |
Report template | External or saved inside the layout's report area. |
Sync requires applicable license/server/data access; ordinary layouts still require their dynamic resources. Embedded reports require saving the whole layout; external templates need separate backup. PDF/image outputs are not editable report-template substitutes.
8.3.2 Licensing and Registration Requests
CREVIALicense.Key is the issued product license loaded normally in About, potentially machine/edition/term-bound. CREVIARig.resp is generated registration-request material, not an issued license and not usable by renaming to Key. Licensing accounts, roles, and database identities are separate. Renewal still needs loading/state checks. Confirm migration procedures rather than deletion/editing. Keep full license/request/machine contents out of public evidence; verify official recipients and secure minimum-necessary delivery.
8.3.3 Settings, Views, and Parameters
Paths are runtime-relative and <user> is the actual generated name.
| File | Contents | Handling |
|---|---|---|
DevXtar.win |
CDPS users/groups/access | Encrypted, UI-managed; not a substitute for publishing policy changes. |
CocDefaultTemplate/<user>/CocSetup.win |
User settings | Preserve hierarchy; old GroupSet.win is not the sole grouping backup. |
CocLayoutTemplate/<user>/GVLayout.win |
Grid view | User/layout/view matching; no encrypted edits. |
CocLayoutTemplate/<user>/LVLayout.win |
Card data view | Separate from GV, not interchangeable by renaming. |
CocDefaultTemplate/<user>/CardImposition.Json |
Imposition | Recheck local paper/card/orientation/gaps/alignment. |
CocDefaultTemplate/<user>/AutoPrintConfig.json |
Automatic rules | Prevent output during backup/restore and verify writeback before enabling. |
JSON describes syntax, not purpose: Records, ExportResults, and AutoPrintConfig are different objects. Manage through normal controls, not bulk extension-based text replacement.
Figure 8.3-1. Show English extension-visible demonstration layout/database/photo/report/exchange files and a limited configuration tree. Do not open license/encrypted contents or expose real projects/user directories.
8.3.4 Data, Photos, and Exchange Files
| Extensions | Identify | Avoid |
|---|---|---|
.db, .sqlite |
Often SQLite; verify actual format | Assuming any db file is SQLite. |
.mdb, .accdb |
Access with appropriate access environment | Suffix-only conversion. |
.xls, .xlsx |
Excel; requirements vary by entry | Restoring a relational database from a flat export. |
.csv, .json, .xml, .md, .markdown, .docx |
Actual exchange structure per 8.2 | Assuming symmetrical import/export. |
.jpg, .jpeg, .png, .bmp, etc. |
Actual entry filter/decoder | Assuming every stage supports identical formats. |
Binary database photos have no necessary standalone file. Folder/interface sources have different dependencies. Preserve naming/ownership and verify alpha/results after conversions. Use native server backups rather than copying active underlying data files; see 6.3-6.4.
8.3.5 Programs, Logs, and Unknown Files
EXE/DLL are programs/components; config commonly stores runtime settings; log commonly stores diagnostics, depending on build/location. Formal Release does not generate project Debug logs. Collect Windows/installer evidence separately.
Before cleanup, record path/time/context and consult maintenance. Do not delete engine companions, transaction markers, or unfamiliar settings to simulate first startup, or upload the whole root. Identify origin/directory, show extension, consult purpose, inspect a trusted copy through the correct entry, and escalate if uncertain. Do not open untrusted layouts/reports/executables.