A little while ago (on one of these NewsGroups) there was a thread about
using Excel as a database and database design. I undertook to consolidate
my thoughts (which were over several posts) on an information sheet. I have
now done this and the first effort may now be seen at -

http://1001solutions.co.uk/Designing_a_spreadsheet.pdf

Regards.

Bill Ridgeway
Computer Solutions

This is quite good. One suggestion: while it's possible to use Excel as a
database, it is not really possible to have multiple concurrent users of the
database, and so Excel's ability to serve as a database (as the word is
generally understood) is rather limited. Given that caveat, looks good.

Dave
--
A hint to posters: Specific, detailed questions are more likely to be
answered than questions that provide no detail about your problem.


"Bill Ridgeway" wrote:

A little while ago (on one of these NewsGroups) there was a thread about
using Excel as a database and database design. I undertook to consolidate
my thoughts (which were over several posts) on an information sheet. I have
now done this and the first effort may now be seen at -

http://1001solutions.co.uk/Designing_a_spreadsheet.pdf

Regards.

Bill Ridgeway
Computer Solutions

Thanks for your response and encouragement Dave.

I do say "Of course not everything included here is applicable to each use".
In the scenario you highlight, most, if not all, the design 'features'
should be just as applicable. They would get you there it's just that Excel
is not the right bus for the journey. The piece is intended as a layman's
(sorry, laypersons) guide and most laymen (laypersons) would probably be
using Excel and would turn to Excel rather than Access in the first
instance.

Regards.

Bill Ridgeway
Computer Solutions

"Dave F" wrote in message
...
This is quite good. One suggestion: while it's possible to use Excel as a
database, it is not really possible to have multiple concurrent users of
the
database, and so Excel's ability to serve as a database (as the word is
generally understood) is rather limited. Given that caveat, looks good.

Dave
--
A hint to posters: Specific, detailed questions are more likely to be
answered than questions that provide no detail about your problem.


"Bill Ridgeway" wrote:

A little while ago (on one of these NewsGroups) there was a thread about
using Excel as a database and database design. I undertook to
consolidate
my thoughts (which were over several posts) on an information sheet. I
have
now done this and the first effort may now be seen at -

http://1001solutions.co.uk/Designing_a_spreadsheet.pdf

Regards.

Bill Ridgeway
Computer Solutions

Fair points.

Dave
--
A hint to posters: Specific, detailed questions are more likely to be
answered than questions that provide no detail about your problem.


"Bill Ridgeway" wrote:

Thanks for your response and encouragement Dave.

I do say "Of course not everything included here is applicable to each use".
In the scenario you highlight, most, if not all, the design 'features'
should be just as applicable. They would get you there it's just that Excel
is not the right bus for the journey. The piece is intended as a layman's
(sorry, laypersons) guide and most laymen (laypersons) would probably be
using Excel and would turn to Excel rather than Access in the first
instance.

Regards.

Bill Ridgeway
Computer Solutions

"Dave F" wrote in message
...
This is quite good. One suggestion: while it's possible to use Excel as a
database, it is not really possible to have multiple concurrent users of
the
database, and so Excel's ability to serve as a database (as the word is
generally understood) is rather limited. Given that caveat, looks good.

Dave
--
A hint to posters: Specific, detailed questions are more likely to be
answered than questions that provide no detail about your problem.


"Bill Ridgeway" wrote:

A little while ago (on one of these NewsGroups) there was a thread about
using Excel as a database and database design. I undertook to
consolidate
my thoughts (which were over several posts) on an information sheet. I
have
now done this and the first effort may now be seen at -

http://1001solutions.co.uk/Designing_a_spreadsheet.pdf

Regards.

Bill Ridgeway
Computer Solutions

Dave F has written (on several occasions) "Specific, detailed questions are
more likely to be answered than questions that provide no detail about your
problem." I would like to add another hint.

It is sometimes best NOT to ask a closed question like "How do I use this
function?" This is like standing in the middle of a town and asking "Where
do I get the number 42 bus?" By doing so you've assumed that the number 42
bus is the only service between the two points. Asking an open question
like "How do I get the computer to do this?" lets others advise on other
(possibly better) routes to your destination.

Regards.

Bill Ridgeway
Computer Solutions

Yes, that's a good point. There's more than one way to skin a cat in Excel.

Dave
--
A hint to posters: Specific, detailed questions are more likely to be
answered than questions that provide no detail about your problem.


"Bill Ridgeway" wrote:

Dave F has written (on several occasions) "Specific, detailed questions are
more likely to be answered than questions that provide no detail about your
problem." I would like to add another hint.

It is sometimes best NOT to ask a closed question like "How do I use this
function?" This is like standing in the middle of a town and asking "Where
do I get the number 42 bus?" By doing so you've assumed that the number 42
bus is the only service between the two points. Asking an open question
like "How do I get the computer to do this?" lets others advise on other
(possibly better) routes to your destination.

Regards.

Bill Ridgeway
Computer Solutions