>
>I certainly agree with your comment#3... I'm not looking to lock a user out
>of their own SQL Server totally (just when it comes to my apps).
>I simply wanted to know if SQL backends provided a secure means of blocking
>all users (dba's, consultants, end-users, etc.) from conjuring up a way to
>gain access to the database (assuming the user had full access to the server
>which held the database).
>IMO, this is what a TPS file brings to the table. Nobody can read a single
>file without contacting me, the developer. I remember a few years ago, I
>had a smart cookie try to gain access by purchasing the ODBC from TS. They
>found out later that they still needed the password.<seg>

Johan,

With enough patience, ANY encryption can be broken. The author of this
comment is laboring under a severe misapprehension that somehow SQL is
"less" secure than dbf files or any flat file equivalent. If I REALLY want
to read his files, I will be able to. Forgoing the power and utility
of a server database because it doesn't provide the same kind of security
as he is used to is a particularly short - sited way of looking at it IMHO.

In any event, there are any number of encryption tools that will accomplish
the same functionality if he really requires it.

This isn't an issue of security. This is an issue of a developer protecting his
turf. I have written all sorts of small applications for clients all over
the world. I have NEVER had a case of someone trying to reverse engineer
my products, and I do not believe that it happens all that often either.

Regards

Tim


[Non-text portions of this message have been removed]