Re: Preventing Database for access

Well, personally, I think you are being highly immoral and (which is worse) totally unprofessional. The data is the clients', not yours. And how they access that data, and interact with it, is their choice, not yours.

If your front-end is so crap they ditch it for another, learn from the experience, and become so good at developing front-ends that no-one would *want* to ditch it.

The best you can do now, I think, is to be forthcoming and helpful in assisting the client in doing whatever they feel is best for them. That way, you seem helpful, accommodating, and professional -and maybe they will recommend you to others for precisely those qualities.

Go on in the direction you seem to suggest here, however, and I smell law-suits.

Regards
HJR <gedik1453_at_yahoo.com> wrote in message
news:9692ca3c.0211130114.57237bd2_at_posting.google.com...
> I prepared an application for a corporation with Delphi and Oracle8i.
> Now I guess that they are trying to get rid off my application, but
> not db. They are trying to re-write my program.
> They have a lot of data in the database, and I want to make the
> database my-application-specific-db. Now I changed db components to
> direct-oracle. And I changed the password of the database and I
> embedded the password in the source code. In the direct-oracle
> component application user doesn't have to know the DB password.
> Also I want to make the database more complicated, that they can't
> understand or program. I thought of distributed databases. any
> suggestions?
>
> Any help would be appreciated.
>
> Regards
> John
>
> P.S. I rented my application to the company now I still give them
> technical support and updates. I want to change the database not to
> lose customer.
Received on Wed Nov 13 2002 - 03:31:43 CST