Posts by peace_of_mind

I'm having difficulty understanding what you are looking for. Are you saying you have a project you have coded and want to know how to explain what the code does? That's kind of what I'm getting from your post...

Which aspects of the assignment are you having difficulties with?

http://java.sun.com/docs/books/tutorial/uiswing/components/icon.html

or try this
http://java.sun.com/docs/books/tutorial/2d/images/index.html

You forgot to use sarcasm tags ;)

Someone is scratching their head trying to figure that last post out, I'll bet. heh

Have you even explored the possibility of just doing this within Access? I don't use it much, but I'm pretty sure these features are built-in. What good would a database program be without it?

Something like this? http://office.microsoft.com/en-us/access/HA102051301033.aspx

Let's see your code (in code tags, please).

That is certainly a possibility. The larger problem is keeping up with all of the ambiguous fields like "someTextField999" and it's relation to "randomLabel645". In the long run, designing an object model that manages these things in appropriate collections like Lists of other objects would be a much more manageable way forward.

(Not to denigrate peace_of_mind's suggestion, which is helpful in the context of the huge tangle of UI code that was posted)

No, you are absolutely right. It is quite a mess, and I would hate to have to maintain it. I just figured it would go over better to suggest what little help I could offer rather than suggest starting over ;)

One thing you don't see enough of with people learning to program (and I've certainly been guilty, too) is planning out a project instead of just diving in. I can honestly say that has helped me a great deal since I've begun learning Java. Now I don't draw out a flowchart, but some pseudo-code or just some notes to help organize my thoughts before beginning can be a tremendous help. At the very least I usually come up with a variable dictionary to help keep me from confusing myself half way through a project. A little organization and forethought can go a long way.

You could do something like the following to actually assign these amounts and keep a running total.

double total=0;
            public void actionPerformed(ActionEvent event) {
                if (PizzaCombo10.getSelectedItem().equals("Cheese and tomato")) {
                    priceLabel37.setText("3.50");
                    total = total + 3.50;
                } else if (PizzaCombo10.getSelectedItem().equals("Ham and Pineapple")) {
                    priceLabel37.setText("4.20");
                    total = total + 4.20;
                } else if (PizzaCombo10.getSelectedItem().equals("Vegetarian")) {
                    priceLabel37.setText("5.20");
                    total = total + 5.20;
                } else if (PizzaCombo10.getSelectedItem().equals("Meat Feast")) {
                    priceLabel37.setText("5.80");
                    total = total + 5.80;
                } else if (PizzaCombo10.getSelectedItem().equals("Seafood")) {
                    priceLabel37.setText("5.60");
                    total = total + 5.60;
                }

When using Ms access 2007

What do you think are the advantages of creating a report design (as opposed to just designing the report as you go)? How could creating a report design actually save you time when you start developing the report? How could you determine which fields should be included? Which sections? How would you determine whether there should be sorting and/or grouping in the report?

Can anyone answer these questions?

1.(and apparently also 2.) Time would be the number advantage, I would think. Once a design is created it is much faster to create a report from then on than it would be to do it from scratch each time.

3.Depends on the report. Should be fairly self explanatory.

4.See number 3