Storing data by year

[RRS]

We manufacture several types of vehicles. Changes are made to each of them
every year. We need to develop a database that will store the model name, the
year(s) the model was built, and a list of the drawings that applied to each
model, each year. 90% of the data can be carried over each year. The last
time we tried this, history was lost when updates for the new year was done.
We would appreciate any help.

 

[Gina Whipp]

RRS,

This is a newsgroup for Microsoft Access a database software. It sounds
like you want a database but you are not building one. This would not be
the place to search for someone. You should try your local universities or
Utter Access has a forum where developers post. But if you are looking to
build a database you will have be more specific in your questions. Right
now, you asked us to build a house with no plans except for 'not like it was
built last time'.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[RRS]

Gina,
Sorry, I thought I was clear as possible in a short message. In sentence 3,
I meant we are developing a database. It also specifies the info we need to
store. I planned on a table to store all the models, a table for all the
drawings and possibly a table for years, if this is the best way. Do I need a
table that stores what model(ID) and year(ID) each drawing was used? I have
developed simple databases in the past, however, this one is the hardest I
have done.
--
Thanks,
RRS

RRS,

This is a newsgroup for Microsoft Access a database software. It sounds
like you want a database but you are not building one. This would not be
the place to search for someone. You should try your local universities or
Utter Access has a forum where developers post. But if you are looking to
build a database you will have be more specific in your questions. Right
now, you asked us to build a house with no plans except for 'not like it was
built last time'.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Gina Whipp]

RRS,

Have a look at this and see if it gets you in the right direction...
http://www.databasedev.co.uk/vehicle_details_data_model.html

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

Gina,
Sorry, I thought I was clear as possible in a short message. In sentence
3,
I meant we are developing a database. It also specifies the info we need
to
store. I planned on a table to store all the models, a table for all the
drawings and possibly a table for years, if this is the best way. Do I
need a
table that stores what model(ID) and year(ID) each drawing was used? I
have
developed simple databases in the past, however, this one is the hardest I
have done.

 

[a a r o n . k e m p f]

you could use a real database- like SQL Server--
and I'd reccomend finding someone that knows what they're doing-- it
sounds to me like you've had data loss.. Newbies can frequently cause
data loss.

Perhaps if you used a certified SQL Server DBA / Developer, then maybe
you wouldn't have to deal with losing data.

-Aaron

 

[a a r o n . k e m p f]

PS - I have an application that works almost exactly like what you're
looking for, you shoudl email me at (e-mail address removed) and I can
send you a copy of this application
I wrote it back in 1999.. and it's used to store drawings, for
multiple years, etc

-Aaron

 

[Aaron Kempf knows nothing]

"a a r o n . k e m p f @ g m a i l . c o" wrote:

 

[Aaron Kempf knows nothing]

PS - I have an appetite for bad things. So
you shoudl email me at (e-mail address removed) and I can
do bad things.

 

[RRS]

Gina, that link you listed may be just what the doctor ordered.