Zd wrote:

> Thanks for the code!
> And thanks to tomkrej too for the other example!
>
> <rant>
>
> I was just wondering that in the 21st century, when there are code obfuscators and sophisticated security/encoding mechanisms everywhere, why on Earth is it such a big deal to make a DB unaccessible to intruders?
>
> I mean I can't believe that no one who does serious software development has ever encountered this issue before... Is this the same for other enterprise level databases or is it just a "Firebird feature"?
>
> Protecting their own code should be a high-level priority for every software developer!
>
> </rant>
>
>

How do you suppose any kind of client software would retrieve data from
system tables (metadata objects) if it's unacessible ? Think about
creating a new report using crystal reports.

Sorry, but I think that on 21st century no one would buy a software who
cannot access trough their desired client program (report builders, BI
suites, or even linking the data in a excel sheet).

Another point... Don't take i as a personal offense the same statement
is applied to *my own* software. Why do you think you had such a
brilliant data model that cannot be looked by any other person ? Do you
really think the most important point is the implementation detail ? I
don't think so, the most important thing is the big picture, the idea as
a whole, not the detail of implementation. And as long as anyone use
your software he would understand the concept of your idea and that's
all he needs to make a clone.

see you !

--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br