[AccessD] Names or numbers?

Gustav Brock gustav at cactus.dk
Wed Aug 4 08:20:16 CDT 2004


Hi Roz

That's really a matter of taste. I see both points but wonder why he
doesn't go to the end suggesting random numbers for the details.

It's a bit like giving tables numbers for names instead of friendly
names. Also, who would those be that would create "arbitrary &
meaningless character codes"?

You could compromise by creating a Select All query for each table and
name the query as you like - then use that and not the table.

/gustav


> Dear all

> I am currently engaged in an argument with a contractor over the naming of
> details in our database.

> His argument is that since the actual names of the details will never be
> exposed to the ordinary user, we should just give them numbers; X0000001,
> X0000002 and so forth. X denotes the current phase of development, another
> whacky idea of his. The 'friendly' names are held in a lookup table.

> Personally, since I have to work with these details on a daily basis, I
> would like the code to be a combination of categorisation, e.g. using the
> 1st two characters to describe the position / type of the detail, say XC for
> claimant details and XD for defendant details and XA for admin details,
> whilst using the other (up to 6) characters to describe the detail, say
> XCDOB for claimant's date of birth.

> The contractor's contention is that people will make up arbitrary &
> meaningless character codes which will be confusing, whereas the numbered
> details will be in a sensible sequence.

> a) he is not proposing to leave any gaps in the sequence for later insertion
> of related details
> b) I don't see how a number is going to be less confusing than an alpha code
> c) we can still use the lookup table with the alpha codes if needed

> Has anyone got any thoughts on naming conventions? Any experience of fully
> numeric naming systems that they can share? I have the authority to overrule
> him but this is a really big project so I want to get it right, and he is
> (theoretically) a lot more experienced than I am. He just hasn't come up
> with any convincing arguments.

> TIA

> Roz




More information about the AccessD mailing list