A bit difficult to figure out...

at first: the total on-line documentation is about 12 pages and tells you WHAT you can do and WHY you might want to do it, but not HOW (hence 4 stars). Took me several hours. But once I got it, it really shines. Quick, appetizing, it walzes through changes in schema without a hitch or complaint. Easy reporting, with the ability to save report formats. Full of lurking sub-menus which keeps the interface uncluttered, but remember: if ‘lost’, always try CONTROL-CLICK!!

Having spent more hours and developing more functionality, I have to say that this is some piece of systems’ programming. With all my changes and experiments, it never hung. It has the ability to nest one table inside another (composition) that is elegant (for instance, the maintenance log items for each piece of machinery). Then, if you ditch the machine, you get a cascading delete (yes, I know, very bad for referential integrity, but here it’s just fine).

This is not even on the same planet as a flat-filer––with some planning, you can achieve 2nd normal form. Worth five stars.

And get this: I sent an email to support (in Germany, in English (which embarrasses me, since I’ve been working on German for about five years)) about delinking an item related in error. I got an answer, in perfect English, brief and to the point, in less than 12 hours. The answer: use the little menu and pick de-link.

The illustrated examples are in German.

hr1832 about Ninox Database