Linking Field

[Ray]

Hi All,

Ok I know their are allot of controversy about when to use
numeric field's ver character fields some would say only
use numeric fields when using calculations with the field
others would say does not matter but I would like to know what most would recommend hear.

I have a field that is hidden from the user that I use for linking to other tables and this field is auto-incremented
and with the discussion�s about padding field's that are setup as char field I would like to use numeric field's
Instead - What�s your thoughts?

-Ray

[DaveM]

RE: Linking Field

Ray,

I use an incremented field for linking also. It is not hidden, but is not accessible to the user. I use a numeric field like you do. I have experimented a lot with this and it is a logical thing.

Dave

[Ray]

RE: Linking Field

Hi Dave,

Thank you for the reply, what size do you use I know this is elementary school talk but I like to get feed back to see if I can better my thinking.

-Ray

[Dan Blank]

RE: Linking Field

Hi Ray,

I use both characters and numbers. Basically it depends on the use I have planned for the table. It also depends if I am getting data from someone else's database. Then that determines which type field to use.

Actually I have a few tables that I have both character and number in. I get tired of creating similar tables to hold similar data, so I may link the same table to other tables using different keys.

As to the width. I typically use 7 spaces. That is 9,999,999 possible records. So far I have only come close to half that amount - once.

Just my way of doing things.

Dan

[Ray]

RE: Linking Field

Hi Dan,

Thank you for replying I will consider using numeric because it only hold numbers for linking to tables I will wait and see what others say.

-Ray

[Cheryl Lemire]

RE: Linking Field

Hi Ray,

I am a character auto increment person myself. Coming from the old time school, numeric should only be used for calculation purposes ... ie zip code and phone numbers are typically character and not numeric. Character fields offer more flexibility.

As far as field size, I have been using 10 primarily because I prefix my auto increments with characters and of course with Dan's food for thought, 7 is great thus allowing 3 more characters for a prefix. The character prefix is another reason I choose character over number. I may not want a prefix initially but might find out down the road that one could be helpful.

I don't like to burn bridges or close doors :)

Cheryl

[Ray]

RE: Linking Field

Hi Cheryl,

Thank you.

-Ray

[martinwcole]

RE: Linking Field

you can definitely use a numeric field as a linking field. I have a whole gobbledigook of customers using numeric fields as the primary linking field for the entire application.

a word of caution, though, I personally don't recommend using autoincrement fields. I manage the increment myself - see "Learn Alpha" for examples.

that said, most developers do not use numeric fields for linking, and many use autoincrement. but, because I have so many clients, and many join their remote offices, i can't take a chance. if the autoincrement ever bites you, you will most likely never use it again. I got bit once several years ago, and it took me many many many hours to fix the data.

also, if you archive records, you can't use it, anyway. say you archive the last 50 records, the next available number from autoincrementing is one that already exists in the archives!

[Ray]

RE: Linking Field

Hi Martin,

Thank you for the reply, I will think this over I know their are many mixed motion's about using a numeric field
when it will not be part a mathematical functions however
that said this makes the most sense because it will only increment number's for linking tables and y allow format it for character if only numbers will be used.

If I use a character field then I need to make sure I pad
the field with 00000001 and if I don�t use character field the I don�t need to pad.

-Ray