Another Approach to Design

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Some of you might recognize this project, since it has been over two months
that I have been struggling with the design and I am still not close to being
there yet.

The small backpackers hostel in Panama.

My question is a general one, regarding design.

Should I COMPLETELY ignore the fact that eventually all my data will enter
my tables via forms and first just simply work on the tables?

Then, once all my tables, joins, junctions and relationships completely set
up, then try to get all my forms and reports in working order?

Would focusing simply on tables clear my head?
 
andreainpanama said:
Should I COMPLETELY ignore the fact that eventually all my data will enter
my tables via forms and first just simply work on the tables?
Yes.

once all my tables, joins, junctions and relationships completely set
up
Click to expand...

To your list I'd add 'constraints': NOT NULL ('required'), DEFAULT,
UNIQUE ('do not allow duplicates'), FOREIGN KEY/REFERENCES
('relationships, enforce referential integrity'), CHECK ('validation
rule'). The aim is to get to the point where you cannot enter 'bad'
data into the database, even when you try (and you should as part of
your for testing).

You can then start coding your front end application in the knowledge
that a bug cannot corrupt the data. The aim (from a data point of view)
is to get to the point where database constraints errors are not
raised; put another way, if data fails to be modified and a database
constraint error is raised you will know the source of your bug is the
front end code. Without

Jamie.

--
 
Back
Top