Subject [IB-Architect] Fw: Mischievous SYSDBA
Author David Schnepper
Tim -- requesting a point of clarification:

Does this include backup? transaction recovery? database verification?

(And THANK YOU for taking a stab at defining the problem!! We've got too
many programmers here -- and programmers like to dive in and fix the


-----Original Message-----
From: Tim Uckun [mailto:tim@...]
Sent: Tuesday, May 30, 2000 7:38 AM
Subject: Re: [IB-Architect] Fw: Mischievous SYSDBA

At 09:46 AM 5/30/00 -0400, you wrote:

>There are lots of ways to solve most problems, but only if the
>problem is well understood. So, once again, could somebody make
>a stab at a clear problem definition. Not a prospective solution --
>just the problem.

I don't want to speak for everybody but here is my wish in a nutshell.

There ought to exists a mechanism such that only the application I have
written should have any access to the data and schema.

That's it. The file ought to be utterly useless to anything and anybody
other then my application. My application will interact with the data and
show the results to my customer if, where, when and how I want.
Tim Uckun
Mobile Intelligence Unit.
"There are some who call me TIM?"

Was the salesman clueless? Productopia has the answers.

To unsubscribe from this group, send an email to: