Software

Ask something
Discussion Locked

i want to develop a simple database client solution using microsoft access

0 helpful
5 replies

by fkeshun

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
my company uses ms excel and word for most of it operations.Information flow in the company have become something else.Everyone keep information from the fellow colleague and as such making work come to a stand still sometimes. As the IT officer i deem it as privileged to save the situation and to help the company reach its goals.But the problem is guys am too much tech wise and knows a little about Access and want to use that as platform to solve this problem.Excel is the main the doc we work on and word too actually the two are what we use in the office most at times.what i want to do is that i want to be able to link those files to access database as well as every designation have access to his or her file without inferring with another file bringing to bare the company now have an accurate place of saving their information where as anyone looking for a particular information too can have access to that information without any problem. I really need help on this so please try as much to help

5 replies

by robo_dev

as a document management system.

It does not work that way. Access is a simple single-user database used to store database records, and attempting to use it to for other purposes would not work well.

An application used to keep track of documents is called a 'document management system'.

by terry

Access databases are multi-user out of the box. To say Access is simple is totally wrong. Access as well as being a very good database also has one of THE best reporting systems going. We have developed a document management system using Access. It started as an Access database and evolved into an Access project (Access front end with SQL Server back end). We also have Registers, Sample Analysers, Phone Directory (with WYWO and Who -is-in) & I have personally created ticketing systems, Production Scheduling... The list goes on.
Simple it is not. There is a steep learning curve but, once mastered, Access is very good.
Purists love to hate it (some people even hate Windows - quiet smile). But there is absolutely nothing to match it for developing an excellent user interface quickly.

by tony hopkinson

simple application and simple backend are two competely different animals.
An access db is file, it's multi user capability is that of the OS, which given it's windows is a shed load more problems.

Last database I created for sample analysis, 12 tables, longest relationship chain was two. Twenty five users, three sets of privileges. About as simple as you can get.
Slight sticking point for access. 22gb after six months, requirement ten years.....

Horses for courses....

by tony hopkinson

To have a single reference location. Thatis access's greatest weakness, along with multi user, which as far as I can make out, you also want.
You want either a document management system, or for simple and cheap (ish)

A shared drive.
A web site with upload and download.
Probably the best solution of all without going overboard a wiki.

I can't see any reason whatsoever to use a database far less asingle user desktop one.

by terry

Horses for courses is correct. For 25 users I would not be thinking Access but SQL Server unless the 25 users are occasional users. In an enterprise how many databases go over or even reach 20GB and how many databases are required?
At that stage we would migrate (migratation is quite reasonably facilitated) to SQL Server AND the front end can then still be Access which gives excellent reporting capability.
But! Let's go back to the original query. Access is multi-user, its security while also limited, is adequate for in-house and would do quite adequately the original query. I know because we have one in place.
BTW: 12 tables, 2 reln, 3 sets of priv may be your sticking point, it is not that of Access.

This discussion is closed to new replies.