On 06.02.2013, at 19:38, Ramsey Gurley wrote:
> May I begin by saying: That design sucks :-P If there's one really big 'n'
> and a bunch of really small 'n's, the customer going to waste a ton of paper.
> Plus, long text in a narrow column? Srsly?? ZOMG, I want to die noa!
>
Well, no, it does
May I begin by saying: That design sucks :-P If there's one really big 'n' and
a bunch of really small 'n's, the customer going to waste a ton of paper. Plus,
long text in a narrow column? Srsly?? ZOMG, I want to die noa!
Don't let them design. They don't know what they're doing. Let them tell y
Folks,
I need some good ideas. I have basically the following model:
PRODUCT (code, name, some other attrs) <-->> STATEMENTREF (status) <<-->
STATEMENT(text)
STATEMENTREF is a join table that has one attribute (so it is not a simple m:n
join). The customer wants an excel file looking like this
