Unique Number to Relate Tables

[CharlieB]

I am not a programer and database stuff goes over my head. However, we have a need for a database application to keep information on loan draws that we are now keeping in Excel files (many many files using Macros to simplify Secretary's input). I have tried in vain to do this in Access 97 and was hoping for better results in Access 2000. One big question is that I need to use a unique number that contains letters (ie they will be street address like 5215 Alamosa - can I use letters and can I use spaces (I can live with no spaces)). In 97, using letters was not considered good. Does 2000 overcome this or am I still at somewhat of a dilema in that requirement.

Lost my copy of Access 97 when we upgrades computers and I am hopefull of getting Access 2000 next week (we still use Windows 98 - therefore Access 2002 not in the picture at present - I know, dumb, but not my decision).

Remember, no formal training in database programming - so don't blast me too much.

 

[Rob.Mills]

ARE YOU OUT OF YOUR MIND?? Just kidding. Just had to blast you a little.

In all my experience I've never come across a situation where I needed the primary key to have alpha characters. And if you know how to join tables in queries then you probably never would.

But if you want to give it a go then set the ID field to text and set it as the primary key. You might want to consider giving it an input format.

 

[SAK]

Maybe I am missing something here, as my knowledge of Access has come informally from text books and the good old help file.

But, for the apps I use, where I set a primary key, the data can be about anything I want it to be, as long as it unique, obviously.

For example, one table has the names of groups that belong to our association. Each group name is unique, thus I make it my promary key and relate it accordingly to other tables that pertinent info.

So generally, as a rule, I use text based primary keys and rarely autonumbers for the PK.