Do not let any software impress you!

Only let it convince your intellect.
Slider img 1
Do not look for a business paradise!

It is a waste of time.
Slider img 2
Only yourself can push you uphill.

There is no easy road to prizes.
Slider img 3
Productivity is the name of the game.

And you have to conquer it.
Slider img 4
As long as you understand it,

you will start to build your know-how.
Slider img 5
We can help with that.

We have the tools and the method.
Slider img 6

Mykosmos/BOS Developing Cycle



Mykosmos/BOS suite contains a fully programmable module named kosmos/BOS Developer. We can use that by a developer (programmer) to script processes, script scheduled activities, provide the necessary database schema, design forms, menus, and whatever type of kosmos/BOS resource is needed to complete the final application.

First-time installation to the target server

After the first process is scripted and tested is time for the first time installation to the “customer‘s“ server. In this case, the developer has to “select“ from the “kosmos/BOS Developer“ the right project (if it develops for more than one customer) and then press the “InstallServer“ button. That has, as a result, to create the file InstallServer.exe into the project‘s directory. If the database used is MS-Access, then there is an option to include the database‘s MDB file into the InstallServer.exe file.

After the building of InstallServer.exe, the developer transfers this file to the customer‘s server. There the InstallServer.exe is executed, and the steps directed follows. The final result is to have the kosmos/BOS Application Server installed in the customer‘s server. Furthermore, if we apply the option for database (MDB) inclusion in this first build, the database is also transferred. If we are using the MS-SQL Server database, then the installation and transferring of the database are performed manually.

Now that we finished this first-time installation of the Mykosmos/BOS Application Server, we have to install the kosmos/BOS Clients in all Associates (Users) Personal Computers. The InstallClient must run in the user‘s terminals. In this client installation, we must provide only the server‘s IP Address and the Communicating Port.

Successive installations to the target server

After the first time installation to the target server completes (and the “customer‘s“ associates are familiar with the use of the first scripted procedure!), the developer continues to script a second, third, and so on...procedures for the customer). Thus, the installation of the following work to the target server follows the same path.