Starting FAQ

Why to use kosmos AutoPilot??

Because by using only one tool you can build smarter applications, easily supported and sooner delivered. Check the demo applications!

kosmos AutoPilot is a Developer's tool that produces an executable?

No there is no executable producing. In kosmos AutoPilot there is only one executable, the "kosmos.exe". This executable is the program that acts both as "Server Application" and "Client Application", but not only. "kosmos.exe" runs also as a Developer's tool in order to "develop" the final application for the customer.

Which is the executable that uses the developer in order to build an application?

kosmos.exe

Which is the executable that runs on server computer, in a delivered application?

kosmos.exe

Which is the executable that runs on client computers, in a delivered application?

kosmos.exe

Where do forms, reports, menus and scripts, that the developer designs and writes, are stored?

All those (forms, reports,...) are named resources and they are stored as small files into the same folder as "kosmos.exe". The clear result for that is enhancement of teamwork programming and very easy customer support (the new report or the faulty form can be e-mailed to the customer!). To use a parallelism the "kosmos.exe" and its resources from one side and a web-browser with HTML files from the other.

A database is required and which?

Yes. Evey kosmos AutoPilot application works with a specified database. Specific information is stored in about 30 "system tables" (with names started as "AU_*"). Currently are supported MS-Access and MS-SQL Server. Oracle is coming soon (using the same "kosmos.exe"!).

I need special programming in order to have Document Management?

No programming at all. All applications that build in kosmos AutoPilot have inherently the capability to store and attach any kind of document (file) that the operating system (windows) supports. The documents are stored compressed into the server computer and can be related/attached to any record/form of the application. That's simple! Check it in demo applications.

How can I use kosmos AutoPilot with an an existing database?

You can select from the "Downloads" page the kosmos AutoPilot Developer. After downloading you install it against the specified database. Then automatically "system tables" are created into the database (backup it first!). The database schema with any relations between tables is extracted and stored to the "system tables". A browsing form and an editing form (with searchable drop down lists for the foreign keys) are created also for each table of the database. A typical report also is created for each table of the database. Finally a menu is created that calls all of the above forms and reports. The next step is to login into the "instantly created application" by using "admin" as a user name with a blank password.

Now you are at a good starting point in order to further develop the "instantly build application". You have at this point already understood that the application is also and developing tool for that application!

How to prepare an existing the MS-Access™ database?

Define for all tables “Primary Keys”. Go to “Relations” panel and define as many relations for the tables as possible (before the installation of the kosmos AutoPilot)

The kosmos AutoPilot Client installation is even faster. By providing the server’s machine name and communications IP port, the installation in one pass creates…

A client’s resource directory and copies…
all the resources from the server and …

…the kosmos client is ready to run.

Does the kosmos AutoPilot installation changes the database?

A little. The installation of the kosmos AutoPilot adds to the database about 30 tables with names starting with “AU_”. Nothing else happens to the database.

All browsers, forms, (*.FM) reports (*.RT), menus (*.MN) and database schema (*.DB) are small files that remain on the central resource directory. These are used in the server’s user interface or copied as the user interface of the client applications.

Why kosmos AutoPilot installation can not see all the tables of an existing database?

The tables of the database that are put into the database schema of kosmos Server must have a Primary Key assigned. Otherwise are not visible to the kosmos Server.

Why the foreign keys are fewer than the number expected?

In order for a field to appear as a foreign key field, the relation with a table must be defined on the “Relations” of the MS-Access™ menu (before the installation of the kosmos AutoPilot).

Why some queries do not return results?

Maybe the Fetch Row Count is big and the Fetch Timeout is small, so the query does not has the appropriate time to execute.

How to change the returned count of records?

By right clicking the mouse select Developer->Application->KOSMOS.APL and go to to “Fetch Records”. The default value is 60 (60 seconds). Change it as you wish.

How to change the timeout of a request?

By right clicking the mouse select Developer->Application->KOSMOS.APL and go to to “Fetch Timeout”. The default value is 60sec. Change it as you wish.

The user has exited the application abnormally. Go to Menu->System->Users. Select the specific user and blank the field Status.

What if I need more information”?

At supkosmoskosmosbos.com you can get more information.