This applet is a completed sample from Tutorial 10: Jumping from the Form of one database to the form of a different database. The files in this Applet show how the databases should look and function once the Tutorial is complete.
To read the Tutorial associated with this Applet visit:
These are my first steps in building a relational database in HanDbase. There are two databases:
- Library details (this is the linked database, to control lending and returning of books)
The circa 430 books are actually my books. By the way, it was so funny to review and populate the database, because I "discovered" a lot of books that I thought were lost...
If I click on a book in list book, it goes to the details database and show this book's lending s, pending or complete. Or shows nothing if there are no lendings.
I have now to test everything to see the hiden bugs. The English translation was just made to send to you
This database was designed to demonstrate a way to figure out the month of a date field. The concept uses this idea:
Take the date and do the following calculation: Date Mod 365.25 That will give you the number of days into the year. 365 days are in a year, but every fourth year is a leap year, so the .25 is added.
Now you have a number from 0 to 365. To get the month, you'd have to do a series of conditionals. Something like this:
If DateMod field (the calc field above) is greater than 31 then output is February, else January.
If DateMod field is greater than 59 then output is March, else output is previous conditional.
If DateMod field is greater than 90 then output is April, else output is previous conditional.
The example has a date field where you can pick a date and then a conditional field that is visible showing the month of the year. A few caveats:
1. It uses up a bunch of hidden calculation and conditional fields. You'll need about 13 extra fields in your database to have room for this.
2. If you are in a leap year (such as now, 2012) the number in the conditional for February onward need to go up by one, as I did not account for the leap day in 2012. On other years, this should work fine as is.
3. September is one character too long for the conditional output, so I abbreviated as Sept
You can then select a view to filter based on the month, so you can see all records that fall within the month you're looking at.
As Confucius said there is always a person I can learned from. That is true that my surrounding full of Guru who an give me advice, an internal voices of their opinion, and comment on me, guides me. With this I had created a My GURU to advice me when I got into problem which I need guidance.
First of all, a notes to write down your concerned, and the associate factor like what,why,when,who,how and a sketch board for something cannot be written down.
Secondly, I have invited my Guru to give their comment, my guru are my father, my admired superior, my friends, my wife, and other guru who will pop up along my live journey. I will be assumed myself in each guru position, and imitate the way they talk and answer question.
1) It is not necessary that all the guru must give advice.
2) It must not be too formal
3) User can create their own favourate Guru like Stephen corvey , Mahatma Gandhi, or any other great man you admire to sit in circle and give you advice.
This is a sample database that shows one of the many ways to generate pseudo-random numbers based of a (Time) seed and a calculation (Calc field). Database developers will find this useful when creating their databases that issue trouble tickets or any kind of custom key.
The database includes a few sample series with specific bounds, please refer to the field (DB Properties) to see how they are setup.
The random number generation is very weak. It's more a sample of things that can be done than a complete solution. Please don't use for encryption or any mission critical function.
This database set is an example of how to bring over multiple fields from a parent table/database to a child using the relationship field.
It's a set of databases called Actors and Movies. The main database is actors and there is a first name and last name for each actor. There is a link field to jump to the movies database to show all movies for that actor. The link/linked pair is set up to show the last name from the Actors databases in the Movies database. Normally this is enough to identify the parent record but in this case, the first name should also be shown in case there are two people with the same last name.
So then there is a relationship field set up that uses the link/linked as a pair of matching values to grab the first name and show it. You'll see in the setup that the relationship is set to use the:
Related Field in this database: Last Name (the linked field)
Other Database Name: Actors
Field in other database: Movies (the link field of the parent database)
Show from other database: First Name (the field we wanted to show here)
From Which Record: First matching record. (if the parent database had more than a single match, this setting would let you choose whether to take from the first or last matching record. In this case, there should only be one match since it's a one to many relationship and the 'many' (the movies db) is looking in the 'one' (the actors db) for a match.
Thus, in the Movies database, you see both the first name (via the relationship) and the last name (via the Linked field type) for the parent record.
To address topic in forum: