Recommended Free Tools
This title describes a practical build, but the available source material does not provide the Uniface component design, ProcScript, SQLite connection settings, or version-specific steps needed to reproduce one. Giving a click-by-click tutorial or working CRUD code without those details would risk inventing instructions. What can be established is how to prepare the data layer correctly and which setup decisions must be settled before implementing the form.
Separate the Uniface repository from your application database
Uniface 10.4 documentation says SQLite is the default database for the Uniface Repository. That does not mean your customer records automatically belong in the repository database. The repository stores Uniface development metadata; application data is modeled as database entities in the IDE and must be stored in a database that matches those modeled definitions. See Rocket Software’s Create Table Facility for Sybase documentation for this distinction.
Confirm the database and connection before building the form
Choose where the customer application data will live, then establish how the Uniface installation will connect to it. The available documentation does not establish whether this tutorial’s SQLite connection uses ODBC or another connector, or provide the required configuration values. If your connection uses ODBC, Uniface documentation points to an ODBC configuration-file generator; that reference alone does not confirm SQLite-specific connection steps. Consult the documentation matching your connector and target environment before entering connection settings.
Also confirm the exact Uniface 10 patch installed. Rocket’s Uniface Library 10.4 catalog was last updated September 10, 2026, and some individual pages are marked obsolete and direct readers to a newer library after patch 10.4.03.44. Version-sensitive instructions should be checked against the library for your installed patch.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
Model customer data to match the target database
Model the customer table as a Uniface database entity in the IDE. The physical application database must match the entity definitions; the repository’s default SQLite configuration does not create or validate that application table for you.
Uniface’s Create Table Facility can generate DBMS-specific SQL scripts with /genSql. Its documentation says the assignment settings must match the target DBMS connector version and parameters. The referenced page is specifically titled “Create Table Facility for Sybase,” so it is not proof of SQLite support or a source for SQLite-specific script-generation settings. Verify the relevant facility and connector documentation for your chosen target before generating or applying SQL.
Plan the CRUD component around entity occurrences
A maintenance form needs to present customer data and support creating, retrieving, changing, and deleting records. Uniface’s Handles reference describes handles as references to objects such as component instances, entities, occurrences, and fields; collection and occurrence handles can be used to manipulate entity occurrences. These concepts are relevant when a component interacts with records, but they do not by themselves specify the component layout, ProcScript triggers, or save and delete behavior.
Before writing the form logic, define the customer entity fields, identify the record key, and decide how the component will select and display one or more occurrences. Then implement and test each operation against the configured application database using instructions and syntax verified for your Uniface patch. Do not treat repository setup as proof that the form is connected to the intended application database.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesRank #3
Keep related-data copying separate from normal CRUD
Uniface’s Data Copy Facility works with database tables modeled as Uniface entities. Its documentation warns that copying does not account for referential-integrity constraints; copying related entities without carefully selecting the data can therefore produce inconsistent results. That warning concerns data-copy or conversion work, not the ordinary save semantics of a customer maintenance form.
Quick Recap
Best Value
- Used Book in Good Condition
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
