>I guess I'll go thru the process of getting the client to agree which button should be which bmp.
>

John, that statement alone gives me the willies. You are the programmer, change them if your customer doesn't like a picture, all you will accomplish is hours and hours of wasted time while they discuss the feasability of various pictures, then argure that they didn't realise that you were going to charge for your time showing them pictures.

It basically doesn't matter what pictures you use, so long as they conform to the two vital ingrediences below.

1. they are consistantly used - if you use a picture of a skunk top show OK, then everywhere that you will have an OK button, it must show a skunk.

2. It is visually appealing when combines with other buttons. In other words, coordinate your buttons. Having a red tick for OK and a yellow duck for cancel is not coordinated.

3. DON'T HAVE BIG BUTTONS! they shout! Nice little sexy buttons are the way to go. Have flyover help.

4. Stick with standard windows colours on your forms. Grey doesn't necessarily mean drab, but pretty coloured forms can really get on your goat after a few days use. Use colours on your buttons, that way they'll stand out.

5. Seriously, use Barbara's suggestion of using sunken and raised boxes to group information.

All these require no programming and makes all the difference to a program.

Steve