Recommended Free Tools
This part establishes the database and version decisions you need before building a customer form in Uniface 10. One distinction matters from the start: Uniface 10.4 uses SQLite by default for its Repository, but that does not mean your application’s customer records belong in the Repository. Model the customer entity in the IDE and configure an application database whose schema matches that model.
What this first part can establish
A working CRUD form depends on three pieces lining up: the Uniface entity model, the physical database table, and the connection configuration used by the application. Uniface documentation says application data entities must be stored in a database that matches their modeled definitions. The Repository is a separate concern: Uniface 10.4 documentation identifies SQLite as its default Repository database, not as an automatic destination for every application entity. Rocket Software’s Create Table Facility documentation explains this distinction.
As an Amazon Associate I earn from qualifying purchases.
The available documentation does not specify a reproducible SQLite connection setup, a specific Uniface 10 patch, or the ProcScript needed to implement save, retrieve, and delete. Those are necessary details for a literal empty-IDE-to-working-form walkthrough, so they should not be guessed. This part therefore prepares the implementation accurately rather than presenting unverified code as runnable instructions.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Choose the database target before modeling the form
Repository SQLite is not automatically the customer database
The Uniface Repository stores development metadata. Although SQLite is the default Repository database in Uniface 10.4, application data is modeled as database entities and must be persisted in a database that matches those definitions. Decide explicitly whether your customer table will live in a separate application database or in another deliberately configured target. Do not assume the Repository’s SQLite configuration makes that choice for you.
#1 Best Overall
Make the physical schema match the entity model
Define the customer entity and its fields in the IDE, then ensure the target table has compatible columns and key definitions. A mismatch between the model and table can prevent reliable retrieval or persistence. Rocket’s Create Table Facility documentation describes generating DBMS-specific scripts with /genSql and says the assignment settings must match the target DBMS connector version and parameters. The cited page is specifically titled for Sybase; it is not evidence of SQLite-specific script-generation support or SQLite connector instructions.
Confirm the Uniface version and connection mechanism
Record the exact Uniface 10 patch
Use the documentation matching the installed IDE and patch. Rocket’s Uniface Library 10.4 catalog was last updated September 10, 2026, while some individual reference pages are marked obsolete and point readers to a newer library after patch 10.4.03.44. Version-sensitive menus, settings, and language behavior should be checked against the library for your exact installation: Uniface Library 10.4.
Rank #2
Identify how the application reaches SQLite
Before writing form logic, establish the connection mechanism and its configuration requirements. The documentation references an ODBC configuration-file generator for assignment settings, but that reference does not establish that ODBC is the connection path for a particular SQLite application. If your deployment uses ODBC, configure and verify the relevant driver and assignment settings; if it uses another supported connector, follow that connector’s documentation instead. Do not infer a connector from the Repository’s database choice.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Plan the CRUD workflow around the modeled entity
Once the entity, target table, connector, and version are confirmed, the form’s four operations should act on the same modeled customer entity:
Rank #3
- Create: enter a new customer occurrence and persist it through the configured application database connection.
- Read: retrieve an existing customer occurrence from that database into the form.
- Update: edit the retrieved occurrence and persist its changed values.
- Delete: remove the intended occurrence, observing any application-level relationships and safeguards.
Uniface uses handles to refer to objects such as component instances, entities, occurrences, and fields. Collection and occurrence handles can be used to manipulate entity occurrences, but the general handle reference does not prescribe a particular form implementation. Consult the matching language reference before adopting specific ProcScript syntax: Uniface Handles reference.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Keep related-data operations separate from ordinary form saves
If you later copy or migrate customer data between databases, Uniface’s Data Copy Facility works on database tables modeled as Uniface entities. Its documentation warns that copying does not account for referential-integrity constraints; selecting related entities incorrectly can leave copied data inconsistent. That warning concerns copy and conversion work, not the normal save behavior of a maintenance form. See Rocket Software’s Data Copy Facility reference.
Quick Recap
Best Value
Checklist before implementing the form
- Write down the exact Uniface 10 release and patch, and use its matching library.
- Decide whether customer data is in a separate application database or another explicitly configured target; do not conflate it with the Repository.
- Model the customer entity and confirm that the physical table matches its definitions.
- Identify the SQLite connection mechanism and verify the applicable driver and assignment configuration.
- Use DBMS-specific schema-generation guidance only when it applies to the target connector.
- Test create, retrieve, update, and delete against the intended application database, not merely against a working Repository connection.
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.
