context:
vb6 / ado / adox 2.8/ mdb file format / jet 4.0 provider (not using Access)
trying to design first database
I work for a very small company, detailing building 'components'
There is currently no database usage in our company.
On my own time I'm trying to learn database/ado so as to improve the way we
work.
My first database idea is to have two tables, tblJob and tblComponent
Each job is a building, each building contains Components, each Component
has information I need to track/collate/report on etc.
Currently all files related to a specific job are stored in a folder on
server by jobnumber
server / 2005 / 05001
server / 2005 / 05002
server / 2005 / 05003
etc
initially I envisioned a database for each jobnumber
so in 05001 there would be a file 05001.mdb and in 05002 there would be
05002.mdb
then for the 05001 job I can query the 05001 table and ask about components
on that job etc.
at this point that would be workable with my very small initial design
criteria ideas which are swimming around in my head trying to become
realized....
However, I can also see a larger world view where there would be one .mdb
for the company and each job would become an entry in a tableAllJobs in the
companywide.mdb file....
that would seem to make it easier to ask company wide questions, like how
many components existed in 2005, versus only being able to ask how many
components in job 05001 for example.
however at this point we don't ask any questions like that...
my thought was that as we got more sophisitcated? <g> in the future we might
want to ask broader questions of our data.
thinking that it's easier to set up the database right the first time rather
than add to it in the future as needs evolve...???
is there any reason to set up a company wide mdb rather than job specific
mdbs to allow for theoretical possible future queries even though I have no
immediate need for those kinds of queries at the present time?
any thoughts on which would be a better approach?
tia
Mark