Building a database?

Question

I am the only programmer where I work (summer job) and I am a student with only a few years of programming experience. So I was asked to build a database and I am very excited about this project because hopefully I can learn a lot from this.

Using this database my manager is supposed to be able to assign work (dealing with businesses) to different people within the company using an interface (all workers have a shared drive). When workers are done with that paperwork related to the business, they can check off that its done, add comments at the bottom of the interface, and then move on to the next business. The only experience I've had with databases is some querying with SQL, and I've built GUI interfaces with JAVA. The information on the interface will be populated from Excel so workers know what businesses they are dealing with.

I've done some research and I believe the best way to build this would be building a GUI using Microsoft Visual Studio (Visual Basic) first, then figuring out a way to populate the Interface from Excel. Also because the data is pretty straight forward and not complicated I will be using MS Access to store and track the database. I know this won't be easy, but for all you geniuses out there, is this on the right path? Thanks.

Answer 1

I build Access databases and sell on line. In one of my databases I have an expanded area with date that applies to a single job. It uses an unocked back end that has most of the features of the front end. It centers on a unlimited number of customer having unlimited jobs and each job has unlimited detail. Since it has an accdb file at the back end you can edit it in Microsoft access and make a new to start at the job Level and changing the labels you would be done. Its 50.00.



In any case Microsoft Access is a fine database building tool and rather then sharring the program you would build it with a back end so each person has their own front end and it updates the community back end. Only the programmer needs microsoft Access everyone else you just put a runtime version on their computer (its a free download from microsoft.



http://theinfosheets.com/2014/05/customer-database-with-invoice-appointment-book-and-pos/

Answer 2

I would have to agree with Jeff on this one. Access is perfectly able to create forms and reports itself, so throwing Excel into the mix is just unnecessary complexity (assuming the end user does not have to do number crunching, if/then analysis or the like, which does not sound like the case from your description.)

Answer 3

" I know this won't be easy, but for all you geniuses out there, is this on the right path?" I think here the "right path" is relative to your specific needs. There are many ways to skin a cat so they say.



In my opinion you should really sit down with the stake holders of this project and really get down and dirty with their needs/requirements. Maybe it is as simple as you state it but maybe they are thinking of something more complex. Finding out the requirements to the project (including functions/features) will help you decide on which technology to use to develop it on.



Do you guys not have an intranet site already? Actually come to think of it SharePoint from Microsoft has this feature available out of the box. Is that an option in your network? In my opinion (again depending on needs/complexity) I'd probably recommend doing something more web based. There are a TON of open source projects for project management / task assignment pre-built using PHP and ASP depending on your environment. Take a look around.

Answer 4

Hello



What I don't understand is why are you trying to do it the hard way. Forget about what you have in your mind. Try to use PHP, SQL, MySQL, HTML, CSS.



I have built databases with what I said above, and it's not hard to do. I guess some people struggle to build the kind of database I mentioned above. I don't understand why people are struggling to build databases.

Answer 5

If you're using a database, then what are the Excel spreadsheets for then? Usually people replace a spreadsheet with a database, not use them together.