SOS.
I think your post is ambiguous…
>>The point is pointless because it is a SYSTEM table and designed to work with it.<<
If a SYSTEM table can use Name and be used with it by the system (Microsoft) then why can’t a user use the same Name in the same table the same way? Sure, Microsoft may remover the field Name in future versions of Access but they may also remove VBA as well. If we become overly concerned about the future then we couldn’t write anything.
>>Any other use of it is not good.<<
Why? That to me is just a personal opinion but is expressed in a way that purports to be fact. That is the purpose of this thread, trying not to overly read too much into a posting by anyone.
>>I'm surprised you wouldn't know that RainLover as you seem to have been around a while.<<
Know what, your opinion? Why do you think your opinion, as expressed here, has any more weight to it than anyone else in this thread?
>>Just because a system table has something doesn't mean you can use it in your own tables.<<
What does ‘can’ mean, and who suggested it could or should be used in user defined field names?
>>In fact, that is probably going to indicate (or should indicate) that you should NOT use it.<<
Why? If a system table used a perfectly good name would it also indicate we should not use the same perfectly good name? It is an assumption, on your part, that its use is wrong and therefore its wrong use should not be propagated but that propagation has not been suggested.
The line of text by RainLover was this: -
>>PS Next thing you guys will be saying is that you have Never created a Database that uses the word "Name" as one of the fields in a table.<<
Read it again but read it carefully. Nowhere does it say that we should create a field name called ‘Name’. What is says is that we have all created a Database with a Table that has a field name called ‘Name’.
There is a very important distinction here which I am sure RainLover knows all to well but I will point it out.
We can not change the MSysObjects table and re-name that field name to something which we would prefer, that table is read only. Some of us need to work with linked tables which are also read-only. We can not change a read-only table to suite ourselves; we must learn to work with what is provided.
We can not say to our employer, “Oh! That table has a reserved word as a field name and I have been told I must not use reserved words in tables.”
The end logic of that is that we can not change what we are given and we can not work with what we are given, ergo…no work.
But the person, who is out of work, is not a professional because they are not being paid.
So under the circumstances, the person who uses the reserved words as provided, and can’t be changed because they are read only, is the professional because they are still being paid to do so.