RE: PF Compiled Files with Dictionaries vs. SQL-Created Tables

So if the data entry program formats the data into a string properly at
the time the data is put into the table what is the issue? You then just
need to pull that data and display it. I'm sorry, but I don't see what
you are getting at?


Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777



"caura" <caura@xxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/04/2011 02:33 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: PF Compiled Files with Dictionaries vs. SQL-Created Tables






Rob e.a,

<quote>
Editing of data is the responsibility of the application
</quote>
???

When I define data, I want the data to be clearly defined:
(for me, since it states "define data",
this indicates it has nothing to do with "business logic",
But everything with data definition.
I surely will be mistaken)

As an example:
If I define a bank account, -for me- It should ACT as a bank account.
(and not -as I read in some posts-
"every application that wants to display or print or ... an account,
should do and redo and overdo the necessary editing".

For me not quiet the way to create applications.
If every application that uses certain data should do editing itself,
This is a splendid example of the opposite of "reuse" and "inheritance"
and
"modularity" and all that modern stuff.

=> if I want an "Employer-reference" of a Belgian Enterprise,
It always has the format "0123.456.789"
So I want it to appear as such and this for every user and every
application.
(without the need for special functions as soon as the data is defined)
=> just a simple 1 time definition in DDS and certainly not
"left to the responsablity of any application that would exploit this
data"
(how many formats that would end up with?) .

=> If I want an Identity-number of one of our Members,
I want it to be shown in every application as a only-positive, zero filled
number.
= just a simple 1 time definition, and again please not "in every
application???".

=> a Belgian account always has the format "999-9999999-99".
Easy to define 1 time in DDS.

=> if I want to define a European account,
It should be able to edit it as a European account also:
BE12_3456_7890_1234 (with "_" as blanks)
Not possible in SQL but not possible in DDS either (=character-editing) .

Sorry but for me these examples are just every day data-manipulations for
over 20 years.
And SQL is unable to deliver these all basic and necessary functions ...

And no, I do not see my colleagues nor me defining and redefining such
trivialities in all our applications.


Luc

-----Oorspronkelijk bericht-----
Van: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Namens rob@xxxxxxxxx
Verzonden: vrijdag 4 februari 2011 15:43
Aan: Midrange Systems Technical Discussion
Onderwerp: Re: PF Compiled Files with Dictionaries vs. SQL-Created Tables

I am still waiting for the OP to define what editing they meant.


Rob Berendt