How we work
One project at a time, built around your Forms.
We take on Oracle Forms projects as companies need them, and build what each project needs along the way. The runtime and the move to PostgreSQL run on your own server.
Our story so far
Real projects in Qatar
A supermarket chain in Qatar wanted a fresh start, so we built them a new application on open-source technology. A waste management company and a garage group wanted to keep the screens their people know, without paying for Oracle. Their Forms now run in a browser, on PostgreSQL. A trading company is making the same move now. Each project left us a tool the next one uses.
Tools built along the way
Each one built because a project needed it
forms-migrate
Moves your tables, data and code from Oracle to PostgreSQL, and checks every result against your Oracle before you switch.
The broker
Sits between your application and the database, so your screens keep working, unchanged, on PostgreSQL.
The translator
Carries the SQL in your Forms from Oracle's dialect to PostgreSQL's.
The runtime
Your screens in a browser, with the same layout and the same keys, on your own server.
Your server. Your data.
What you can tell your IT team
- The runtime runs on your own server, one per company. It needs no internet to start, to show a screen or to save a record.
- Your rows never leave your premises. Your database password stays in your own settings, never with us.
- The move to PostgreSQL runs on your server too. After it, your Oracle stays as it was, ready as a fallback, until you switch it off.
- Before the browser screens go live, each one is checked against your database's structure. The check reads no rows.
- The runtime names its own version at any time, so "what are we running" has one answer.