Graphical Interface for Access Database

[raja]

My friend works for an engineering firm, and his boss recently quit. This was the boss that had developed the database they had been using, and their database SUCKED. So, when she quit, one of the big bosses asked my buddy to create a new database that would work a little bit better. Since his specialty is programming, and mine is graphics, he asked me to design a little banner for him to put on the database. Here's what I made for him:

His boss liked it a lot, and they are going to use it. Now, however, my friend wants me to help him design a GUI for using this new database. Since I'm going to have to be doing some of the programming for this project (something which I only have very minor experience in), I need help! Where do I start? How does one go about designing a graphical interface for using a microsoft access database? Please help!

[doctorgonzo]

When you mean a GUI, are you talking about the forms and reports used to access the database?

Designing the GUI is the last part of implementing a database. First, you have to make sure that your database design is a good one. Then, you need to determine the ways that users will need to access the data, and what they will be doing. Then you design things.

Your friend should get to work on the first two things before you get involved at all. Then, once he has a list of requirements (like "I need a report that will display this, this, and this," or "Users need to be able to input this kind of data here"), you can take that and use your graphical ability to make it pleasant to use.

[Force Flow]

Take a look at File Maker Pro.

[sdkfz]

Designing a DB I have found is best when I follow the below 7 steps

1) Overall System Design - in English what is this thing trying to do? Inventory/Billing/ CRM etc.

2) Report Design (Output) What will be the required reporting - this will determine what goes IN in step 3. Taking a lot of time here will make the rest of the steps easier, nothing worse than "Oh yeah can I get a report on X?" and X is not even a data element and you are way down on step 6 already...

3) Data Design - what you need to get #2

4) Table design (relationships) making the data as organized and relational as possible. ie one identifier that is used in all tables (customer number/SSN etc)

5) Field Design (making sure the data going in covers all bases) - is if you have foreign customers then a numerical zip code field won't cut it as they can use alpha numeric zips - my grandad's zip was EX 329 EH in Barnstaple England for example.

6) Form Design - Input of #3 - this is where you will start to come in - making the data entry path easy for the data entry people

7) Menu Design - automation or getting around.

Good Luck -