[AccessD] Data Export Spec - Rev1

<<<
a universal solution as Shamil has in mind
>>>
Gustav,

My solution is not not intented to be universal.

What I propose is to develop a solution, which will allow to not patch the
core code but use pluggable custom classes additionally to the "default
formatter", which use metadata and Format$ function.
Additionally I propose to take into consideration from the very beginning
that data source rows' quantity can be very large in general case and that
developed solution should be ready to work well in such a case too on a
moderate average PC....
Additionally...  a limited short list of proposals may follow - but that's
all - and for the universal solutuion this list promise to be endless....

<<<
Clients are very pragmatic.
>>>
Yes, I know.
And I saw it many times and I'm continuing to see how this client's
pragmatism results in bad software and then they blaim bad developers.
I'm pragmatic too I think - let's try to educate clients step by step? IT
industry is mature enough now for this clients educatiion work. (Yes, I know
I sound too optimistic, real life isn't like that, Been there, seen that. Or
I'd better say I'm still there and see that everyday troubles in my own work
with "badly educated in software development" customers. It's not easy to
convince clients to wait a little bit more for end results they needed
"yesterday". It's even more complicated to convince them to pay today for
additional work, which results in their own savings in long run. It's often
necessary to invest our own time. But when customers see good final
results then the next steps for the next projects are easier...)

It's just silly (as John said) to see how resources are wasted when
relatively small additional efforts used on project envision and solution
architecture design phase result in savings in short and long runs and in a
flexible ready for future changes solution, which may find application in
the areas, where "quick&dirty" will never find....

Recap
======
1. I'm not pretending to develop a universal solution.
2. I'm pragmatic
3. I believe(I see) that IT industry is mature enough for simple but
flexible, ready for future changes, mature software design and development
solutions.

Shamil

----- Original Message ----- 
From: "Gustav Brock" <Gustav at cactus.dk>
To: <accessd at databaseadvisors.com>
Sent: Friday, October 21, 2005 2:11 PM
Subject: Re: [AccessD] Data Export Spec - Rev1


> Hi John and Shamil
>
> Interesting to follow this thread. It demonstrates what happens when you
move from a fixed to-the-point solution (like my example) over a generic
solution as John is suggesting to a universal solution as Shamil has in
mind - and all the considerations that move causes.
>
> I'm pretty much in line with Shamil on this. However, time has shown me
that such thoughts most often are over the head and/or pockets of the client
and you'll have to compromise. Clients are very pragmatic. But during this
at least you have a nice intellectual time with yourself realizing that you
are ahead of the client!
>
> /gustav
>
>
> >>> shamil at users.mns.ru 21-10-2005 11:09 >>>
> <<<
> It is intentionally (or intended to be) that simple.
> >>>
> OK. I see now.
> And as far as I see the only source data transformation method is to apply
> specified format.
> This looks of rather limited applicability.
> I think with a few additional efforts this program can be made to use
> additionally runtime pluggable data formatters - then it would be more
> useful.
>
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com