>Hi Erik -
>Thanks for the response:
>
>to answer your first question, I want my primary keys to be character representations of numbers.
>
>to answer your next question, the reason I decided to change my primary keys from numeric (which is working just fine I might add!) to character data type is b/c some of my fields that are indexed contain characters. For example, I have a field called jurisdictionID that isn't numeric......it is character.
>
>Another reason is b/c when I am creating combo boxes with drop down choices, when I make a selection it puts a number in the box and not the descriptive word. For example, if I had a caterogy drop down box and I scroll through the list I could select:
>
>1 Jeans
>2 shorts
>etc.
>
>Well, if I select Jeans, the number one is placed in the box, not jeans. I would much rather view the word on screen than the numeric number.
>
>
>Am I way off base with this, or should I just stick with the way I have my app set up, which works fine with numeric data types for my primary keys.
>
>Come to think of it, my problem isn't lying with my primary keys. The problem is with my "other" indexed fields. I have each one of my indexed fields set up with a numeric data type. I should probably just keep my primary key numeric and change my other indexed keys to character.
>
>I think I worked this out just typing! Actually, I feel a little silly. For some reason I had it in my head that it was my primary keys causing me problems, but I believe it is all my regular indexes I have set up as numeric data types. I think I am losing it!
>
>Talk to you later Erik
>
>Jason

I'm glad you worked it out. :-)