Making applications look great!

davesmith202

Employee of Access World
Local time
Today, 02:15
Joined
Jul 20, 2001
Messages
522
What do you do to make your MS Access applications look great?

I always:

1. Have Forms in dialog view. Think they look nicer.

2. Remove Close, Min, Max buttons.

3. Leave with default grey for backgrounds.

4. Have the Form's name in the Windows title area rather than using a Text control.

Your turn!

Dave
 
Theres an obvious answer to your question. Drop access as a front end. It's the worst gui.

Jon
 
Re: Re: Making applications look great!

mission2java_78 said:
Theres an obvious answer to your question. Drop access as a front end. It's the worst gui.

Jon
Despite what he says, we know Jon really loves Access. :D
 
Please excuse Jon... he knows not what he says....:D

truth be told Jon is a recovering Access-a-holic and is currently enrolled in a Microsoft 12 step program...

Kev
 
Kevin_S said:
Please excuse Jon... he knows not what he says....:D

truth be told Jon is a recovering Access-a-holic and is currently enrolled in a Microsoft 12 step program...

Kev

:D :D :D
 
Kevin_S said:
Please excuse Jon... he knows not what he says....:D

truth be told Jon is a recovering Access-a-holic and is currently enrolled in a Microsoft 12 step program...

Kev

It's a recursive twelve step program..thank you!
:D :D
 
Wait, I think I've seen that before. Is it something like:
Code:
Sub Microsoft12StepProgram(input) as Reinput
On Error DoNotPassGo, DoNotCollect$200
Dim Access.Programmer
Dim RST as RecordSet

    Set Access.Programmer=Jon
    Set RST as New NeverEnding.Recordset

    RST.open

    Do until RST.EndOfLife
         Microsoft12StepProgram(Jon)
    Loop

End Sub
 
application suggestions

1. I use the switchboard. So, when I run out of room for more options, I group things together, like reports. Or, kind of reports. Sometimes, I group all of the 'background' forms together.

2. I use color backgrounds on forms, but I choose light colors. So, when I print (color printer or not), I use less ink and still make it look nice. I put a text box 'Form Label' like 'Patient Records' on the form in a dark color that compliments the light background color.

3. I line up info on forms in logical groups -- like client#, client last name, client first name, client middle initial on one line; then street address by itself; then city, state, zip together. Sometimes, I draw a box around similar type info.

4. I bold all field labels.

5. I bold all button labels, too. And usually, make them the same size and line them up. If I am doing a form of reports, I group the report together (dailys, weekly, special) and include a text box label.

6. I try to put the same buttons on the forms in the same order. My users like buttons for Add, Delete, Print, Close. Also, I try to make the forms fit on a page of paper, because quite frequently the users want to print the page.

NOTE: A complex form with sub-forms usually needs a print report setup to handle this, or it ends up trying to print ALL of the records.

7. Rather than a report header, I put page headers on the reports -- both to allow me to help the user when they have questions/problems and also for the user's reference.
 
dcx693 said:
Wait, I think I've seen that before. Is it something like:
Code:
Sub Microsoft12StepProgram(input) as Reinput
On Error DoNotPassGo, DoNotCollect$200
Dim Access.Programmer
Dim RST as RecordSet

    Set Access.Programmer=Jon
    Set RST as New NeverEnding.Recordset

    RST.open

    Do until RST.EndOfLife
         Microsoft12StepProgram(Jon)
    Loop

End Sub

I like that one :p :p
 
One issue I have always tried to manage is consistency of appearance and usage.

That is, if I have more than one form and the same general function appears on both forms (like a Commit or Cancel option) then the same type of controls are used everywhere that they apply. And no other control uses the same color scheme for any function that ISN'T one of the common ones.

Then, every form has the same color scheme AND that scheme is not a harsh color combo. (My former college advisor liked to use bright chartreuse as a background with bright orange for detailed data. Yechh!)

Establish a consistent data-flow theme. For instance, when entering raw data on a form, pay attention to tab ordering. Make the tab order match the order of field appearance on the form. Do this for any form where you could enter or change data.

Speaking of making changes or entering new data, do not take a passive approach to recording data. Do something visual (why else would they call it Visual Basic...?) so that your users can tell at a glance what they have done. For instance, on one of my biggies, the background of a modified field on a form becomes a light pink color and the letters become a dark red color as soon as you tab out of the field. They stay that way until you commit or cancel your transaction.

Look into using tool tips. Some folks don't like them, but if you use them consistently, they might take the place of building your own help files.

If that doesn't work, you can also try something I did on one app regarding help. On any of my forms, a "GetFocus" event caused that control's extended "Help" information to appear in a "Hints" area that was a part of the form as an unbound text box. The active control's border and label also changed from Black to Magenta while that control had focus. Of course, on firing the "LostFocus" event, the control's color scheme was reset to Black for borders and labels.

Sometimes the issue is merely to provide proper data flow assistance and/or guidelines. For instance, after any action, sweep through your control buttons. Based on current context, make the buttons visible or invisible depending on what is legal at the moment. Along those lines, I have one form where I can put any of nine buttons in a space normally wide enough for only five buttons. But it works because there is no time in the process where more than five options exist at the same time. The buttons "float" because when I make them visible, I keep track of where the last button was placed. The next button pops up into place next to it. The action labels float above the buttons, so the user has one place to look for all controls.

All of these things sound complex, but really it is a matter of building a few (and I do stress FEW) little subroutines to implement each change. Then it is a matter of calling the right routine for each case you have to consider.
 
Command Buttons

We stopped using command buttons. We build icons with a simple icon builder, then line them up horizontally like on a toolbar, and raise them as a command button when moused over, pressed, and perform an action on release. It gives it more of a "web" type feel, also we got tired of fighting the background color for our custom icons when put on a true command button and the user had a a different color scheme.

We also tried to make our forms similar in function and appearance from one to the other, if Cancel/Close functions the same way on one form, it looks the same.

Splash screen on initial load (check backend at the same time).
 
Re: Re: Making applications look great!

mission2java_78 said:
Theres an obvious answer to your question. Drop access as a front end. It's the worst gui.

Jon

If i knew how java worked, i would use it. :D
________
ARIZONA DISPENSARIES
 
Last edited:
I was going to ask what GUi would you sugest for your database stuff? If not access what?
 
Most Access developers aren't graphic artists. And yet 99.9% of commercial graphic artists copy other people's stuff, making a small change here or there and then calling it their own. So do what the pros do; find an interface already out there and bend to fit...

Regards,
Tim
 

Attachments

  • xkatex.jpg
    xkatex.jpg
    66.7 KB · Views: 1,012
So did you use Java to build that GUI in the picture?



Also is there a program that someone can direct me to that will help me learn java visually? I mean if java is a gui there must be a gui to make java?
 
It's VB6, but with controls available for use in Access: a treeview, a listview, a toolbar, and a statusbar.

Regards,
Tim
 
Great GUI

Tim,

Tell me more that looks great and just what i would like to be able to create for my database

Thanks

Dan
 
For me... I do the following...

1. have a black background (form that is nothing but black) have it stretch to the width and height of the screen. I have used some graphics on the background.

2. Have a splash screen that then goes to the main menu

3. All the buttons are graphics that I make, I don't use the pre-designed buttons

4. Try to stay away from heavy graphics can slow down the application

5. Common color/design scheme on all the forms/reports etc.......

6. I also make sure the forms are all the same size, so when you close one or open one they look like they are the same form. I also have the banner, if the form(s) have one in the same spot and cordinates so it looks the same on all the forms.

7. On all the forms I get rid of the selctors/navigation etc....

8. On all the forms I leave a 1 space border around the whole form and have the background black (or what ever color the background is) so that it blends.

Just some of the things I do to make the applications look a little nicer.
 
I like clean simple forms.

) White backgrounds. :eek:

) Small forms that are not maximized unless required. That helps for different screen resolutions... unless you want to set their screen resolution in code... cough... cough...

) For me I never stack exactly sized forms directly on top of one another - an accidental double click makes for a weird expression... or you can disable the default close button on some forms if you do.

) Data flow. Make sure your forms data entry and edit sequence is not faulty or haphazard. Main issue.

) Modal or Pop Up forms can be used for Help on specific individual forms...
 

Users who are viewing this thread

Back
Top Bottom