[AccessD] Tech books ...

> There are two points I'd like to point out (neither of which has a chance
of
> making it). 1.  Have a few overly documented examples if you will - but
> include a bunch of heavy duty
>      code for examples for the advanced programmers - with little or no
> comments.  The documented
>      examples in books are usually too simple to be very useful.  Real
code
> will teach most
>      developers without the comments.

============I include just the code that does the task -- no error handling,
no comments, just the code. I get fussed at a lot by other readers and some
editors -- but I resist. Occasionally, if a particular error is inherent to
the task, I will include handling for that, but only when it's specific to
the task. There's a difference between the two.

> 2.  As there are millions of Excel and Access power users through
developers
> - and sometimes they
>      will be doing other apps - eg. Excel to Access, Excel to VB, Access
to
> VB and/or VB to Access,
>      Access to Sql Server and Sql Server to Jet - consider writing a From
X
> to Y Dictionary.  Eg.
>      From Access to VB, From Jet to Sql Server, etc.

============You'll probably not find any publishers or authors willing to
take on these projects. You need to be an expert in more than one thing, and
that cuts a lot of authors out. Then, frankly... these titles have limited
appeal. Generally, a book needs to attrack a large audience. That's why you
don't see many "specialized" books -- they don't make any money. Neither
publishers or authors can afford to work for free, and that's what would
happen. The book Martin and I wrote is aimed at the Jet to T-SQL audience,
and trust me... I'd be on the streets if that were the only work I had right
now. It's a shame, cause it's a great book.

Susan H.