If you were developing any database system professionally, do you think there are systematic approaches that can be used such that the whole project can be better managed and all grounds can be cover for the client?
Define your tables so there is no redundant data, and that all information stored in a record depends on it's primary key.
Use table relationships to link tables together.
Before delivering any 'final' code to the client, create a rapid prototype that you can demonstrate and get feedback. With few exceptions, customers don't know what they want, but they can tell what they *don't* want when they have something to work with.
Don't hardwire *ANYTHING*. Use preference or settings tables.
Split your database into a front end with code, forms, reports, etc. and a backend (stored in a server) with just tables.
Use queries for everything (e.g. form record sources, report record sources).
Use forms for data entry. If you want a datasheet, use a form with datasheet view.
Use lookup tables (with combo controls) where ever possible.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.