Hi Andrew,

Am Donnerstag, den 29.09.2005, 05:07 -0400 schrieb Andrew Jensen:
[...]
> First - Back to reports. Lots of users of MSA are there because it is 
> the easiest tool for them
> to create reports from their corporate databases. The key word is EASY, 
> but it also lets them
> get more creatinve as their skills go up. This is the hard part of this, 
> MS did a good job of hitting
> the mix of ease and strength, that is a tough thing to get right.

This issue is worked at, as far as I can tell. And for the time until it
fits your needs you can use any report maker out there, try searching
www.sf.net for the keyword and you'll get anything you can think of (and
mostly even more).

> Second - The Query Builder. Creating select queries is only the 
> beginning. Update and delete queries
> are one of the strong points of MSA. At first this seems like more flash 
> then substance, but it really
> is a feature that users make use of. Now add to this the ability to 
> create pivot tables
> and you have a large part of MSA's usability for the non-dba.

Since I stopped using MSA in Version 2 I'd like to ask you, what exactly
is missing here? So far I had no problems building queries in OO.o. For
upüdating and deletion: Design your query in the SQL view and leave it
that way, should be enough in most cases.

Distinction between types of queries would be a good thing, if you file
an issue I'll vote for that one.

> There is an aspect of the data manipulation by query functionality that 
> users I have seen love. The ability to
> undue the changes. OK, so we know this is just a case of turning 
> autocommit off, and doing a rollback.
> But they never had to know that, it is just done for them and they 
> therefore feel safe.

Have you filed an RFE issue for this one?

> Third - Upgrade to the StarBasic tnterpreter. The difference between 
> trying to do a simple task in VBA and
>  StarBasic is striking. StarBasic just must be pulled, kicking and 
> screaming if necessary, away from the API
> and up to a 'business object' (or whatever term we come up with, a high 
> level) level. Simple test, the second
> you find yourself needing to explain what MVC means, you have lost a 
> third of potential scripters! If you also
> have the ability to use the API directly then all the better, but it 
> just can't be the only route.

If my memory doesn't fail or there has been some big restructuring in
MSA then scripting in OO.o is not much more comlicated than MSA.
Microsoft has no good understanding of what should be an object, a
property or the other way round. I really disliked programming MSA.

Your point in respect to OO.o is true, it lacks some form of object
orientation. But for small scripting tasks like making a button do
something this isn't necessary.

People using OO.o base on that level are free to use Java or C++ for
writing their own components aggregating things in an appropriate way.
Yes, I'd like to see BASIC be fully "VBA-like", but the effort to get
there isn't worth forgoing development in other areas of more
importance.

> Fourth - Multi user support. I have no doubt there where good reasons to 
> have not supported this in the
> intial release. But you need to get it in there as soon as possible.

I don't understand why you think base does not support multiple users.
Or what you want to achieve. From the database side if you choose a
server type database there is no problem.

>From OO.o's side: I don't want other to use my personal installation,
and in the sight of privacy this is no good idea.

The only problem I see is to start with a single embedded type HSQLDB
that later on should be used by a multitude of users. For this tasks
there could and should be a small howto telling anyone how to switch
from the embedded HSQLDB to a server type one. In the meantime you can
look at www.hsqldb.org (hopefully this is right ;) how to set the db up
correctly.

Anyway, it's Open Source and you can do to it whatever you like.

Use the source, Luke!

Regards,
Marc



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to