[AccessD] Subdatasheet vs. Relationships?

I didn't mean to offend, and if I did, then I retract my statement
immediately. I reserve my offences for the OT list. All I meant to say was
that relational database design is not within the realm of amateurs. It
takes years to comprehend the meaning of RI, cascade-delete etc.. IMO nobody
can do it in a year. This stuff is complex, which is why they pay us the
ostensibly big bucks. Take Jet or worse SQL 2K. IMO Einstein or Pinker or
Chomsky couldn't grasp it all in a year, though I acknowledge that each of
these are 10 times smarter than I. It took years to get where I am, and
despite my "socialist" (c.f. Hindman) leanings, I am not stupid. This stuff
takes a long time and several failures to learn.

Once I spec'd an app at a month and it took six months to deliver. That was
early on, when I thought I knew what I was doing, but I was very very wrong.
And paid the price, since I was also so stupid as to flat-rate the gig.
Never again. Now I understand the purpose of Use Cases, Functional
Specifications, Flow-Diagrams etc., and would never accept a gig in the
absence of said specs. My position now is, any gig worth money is worth
documenting, and if you won't pay me to document it then document it
yourself, else get another programmer. At the end of the day, I want a
checklist that says, the program must do X, and if I can prove that said
program does X then you must pay me, else not.

IMO, far more important than the code is the agreement. If you ask me to do
X and I do it and can prove it, then you pay me. End If. You of course are
free to say it should happen in fewer keystrokes or mouseclicks, but that's
rev. 2.0, and I expect additional money for achieving rev. 2.0.

My principal concern is that both parties are on the same page. Don't tell
me that "it should enable me to invoice selected customers." After 20 years
in the biz I wouldn't dream of accepting such a contract. Before I write a
line of code, I want to know exactly what screens and options lead to what
other screens and options, and if we can't agree on that, get another coder.
I'd rather repaint my living room.

Arthur


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.510 / Virus Database: 307 - Release Date: 8/14/2003