Thu Dec 11, 2008 9:25 pm Post
Thu Dec 11, 2008 9:52 pm Post
AmberV wrote:Jaysen wrote:BYTW this is one of the things I admin most about Keith and Kevin (the guy who develops Moneywell http://nothirst.com)....
Spoken like a true sysop.
Sat Dec 13, 2008 2:07 pm Post
Sat Dec 13, 2008 6:40 pm Post
AndreasE wrote:I have now downloaded the demo (almost 200 MB ) and played around with it for several hours, read in the manuals etc., but in the moment I am rather disappointed. Panorama does a lot of amazing things, but - as far as I can see - not the one fundamental thing a RDB should be capable of: defining relations between tables. In fact, the mere word "relational" appears only 2 (two) times in the main manual of 1954 pages...
So, no replacement for MS-Access, as it seems...
Sun Dec 14, 2008 9:09 pm Post
bobembry wrote:http://www.provue.com/Panorama/index.html mentions that Panorama is fully relational.
Sun Dec 14, 2008 9:47 pm Post
AndreasE wrote:bobembry wrote:http://www.provue.com/Panorama/index.html mentions that Panorama is fully relational.
It mentions that, but it does not explain in which sense. Because in the forum, you find the explicit statement that "Panorama is no relational database that provides referential integrity".
The question is, however, if one really needs an RDB for everyday purposes. I am contemplating about this in the moment, because otherwise, Panorama is a beautiful product - you feel that the developers love their software and use it themselves (we all here know another fine piece of software that fits in this description, only that the plural is not appropriate).
What I'd like to have a database application for is to get an overview over the sales and earnings of my books over the years, for the different editions, translations etc., most preferable in beautiful charts that show me the highlights (OK, these I know) and the lowlights (about these, I can only guess). To achieve this, conventional database wisdom demands a complex structure of related tables like WORKS, PUBLISHERS, EDITIONS, LANGUAGES, ACCOUNTS and so on (a WORK is the text I write, it appears in several EDITIONS at several PUBLISHERS that may belong to different LANGUAGES, for which I get ACCOUNT statements every six months etc.) - a structure that poses difficulties as soon as, for example, two of my works appear in one edition: so, maybe conventional database wisdom is not the end to all questions.
Hmm... Maybe I should ask this the folks at Panorama...
Mon Dec 15, 2008 9:05 am Post
Mon Dec 15, 2008 9:21 am Post
AndreasE wrote:Hmm... Maybe I should ask this the folks at Panorama...
Mon Dec 15, 2008 11:14 am Post
In total there are 2 users online :: 0 registered, 0 hidden and 2 guests (based on users active over the past 5 minutes)
Most users ever online was 1048 on Mon Feb 06, 2012 9:07 pm
Users browsing this forum: No registered users and 2 guests