Hi Mark

> Date: Wed, 08 Aug 2007 12:28:19 +0100
> From: Mark Stanton <[EMAIL PROTECTED]>
> Subject: Re: Data Strategy
> To: [EMAIL PROTECTED]
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset="us-ascii"
>
> > Yes I follow a more C/S apprach where your only getting the data your
> > looking for instead of all of the data and pick what you need.
>
> Yes, but how do you go about that.
>
> To be more specific about an example, someone on the database may have
> been making payments for several years, but the finance person only
> needs to see this year.  What does the "payments" view do?  Have a
> filter for this year?
>
> Hmmm, talking this "out loud" it's starting to sound like a daft question.
>

I also follow the C/S approach where the user specifies what they want
to see. Unlike most every other system I've seen, I give the user the
ability to construct a where clause. They don't need to dynamically
create a list of fields nor an order by nor a group by. Those would be
required for a custom report. For a data entry screen - the list of
fields is predetermined by design. For searching, the list of tables
is predetermined by design. My users can use any field from any of the
tables in the query. I never get a call like "can you add the middle
name field to the already over-crowded search screen". ;)

I take the user's where clause - which is constructed to look like
parameterized SQL - add it to my hard-coded SQL command and submit the
whole thing as a query. Users love it and programmers say it's
overkill or not allowed because it's not stored procedures. Who you
gonna cater to? ;)

Mike


_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to