I've been given a system/process that needs updating and I'm a little unsure about the best route.
The system needs to track the process of developing promo leaflets, through out the different revisions. It needs to store all the revisions and associated docs for at least 6 years, and some indefinitely.
As a rough estimate there could be around 18k promo's a year, on average the promo has around 150 pages, ie ~3mill docs!
Obviously thats alot
Speaking to people one of them suggested a document management packadge. Now I've been googling around, and I'm not sure if they are suitable! Although there is a lot of documents I don't need to do much with them, cept store where they are. I don't need to full text search them, I don't need to annotate or anything, I don't really need a complicated index either. Though one thing I guess an off the shelve packadge would give is compression and also a single combined viewer. So we would be paying for a packadge that we only use a small part of!
Currently I'm thinking of a SQL backend (which can cope with a 16mill row table can't it?), an Access frontend and some disk space
The reason for the Access (97 for now, will be going to 2002 within 18months) frontend is so I could use its filter by form facility, which I would have to do my self if I used something else.
Anybody have any comments?
The system needs to track the process of developing promo leaflets, through out the different revisions. It needs to store all the revisions and associated docs for at least 6 years, and some indefinitely.
As a rough estimate there could be around 18k promo's a year, on average the promo has around 150 pages, ie ~3mill docs!
Obviously thats alot
Currently I'm thinking of a SQL backend (which can cope with a 16mill row table can't it?), an Access frontend and some disk space
The reason for the Access (97 for now, will be going to 2002 within 18months) frontend is so I could use its filter by form facility, which I would have to do my self if I used something else.
Anybody have any comments?