I have just uploaded this new version by Dan into the feedback folder. I am not
too happy with it in its present form. It is well written and clearly
explained, but I think it goes into too much depth for a GS chapter. It is also
very long and will be even longer if we incorporate the additional
Hi :)
I used to think that Base might need 2 "Getting Started" guides.
1. for people just doing data-entry and normal user perhaps with routine
maintenance
2. for designers building a database and front-end and for advanced
maintenance.
Writing for 1 would be a nightmare due to the huge
What I have been thinking about for some time but never really got
a round to doing:
1. Getting Started with Base chapter containing a flat database created
by the Wizards with the basics of what to do.
2. Base Guide: (first four chapters that is)
a. Introduction to Base: creating a relatio
Hi :)
I like that plan :) I think splitting the guide would be easier after this
incarnation of it is completed. I think we need something solid and "out
there" (released and published on Lulu) before we can really make sense of
exactly what does and what doesn't work well in those sorts of sp
On Sun, 2012-02-05 at 17:15 +, Hazel Russman wrote:
> I have just uploaded this new version by Dan into the feedback folder.
> I am not too happy with it in its present form. It is well written and
> clearly explained, but I think it goes into too much depth for a GS
> chapter. It is also very
Perhaps, but I'm thinking that Base like the other guides will
have people using only parts of the guide. Some will use the simple, and
others with use the complex. So, I wonder about splitting Base or any of
the other guides. Who knows, someone beginning with the simple might
decide to try
Spliting guides woule be DESASTROUS ... imagine someone trying to get help
on a guide having to find the info they need on ANOTHER guide ... sorry
this will not work, it is easier to have a step by step aproach and let
those who need it jump to the sections they want.
GS with BASE whould IMHO be r
