Why isn't there a category for MSAccess
-
Well, mathematically, uniqueness always refers to a specific set of elements. I can therefore easily imagine definitions of overlapping sets with multiple keys that are all unique within their own set of reference, but not within the union of all elements of all sets. To give an example: number plates on cars are guaranteed to be unique within the country that issued them. However, there may be identical alphanumeric sequences that are valid number plates in different countries. Since in many countries number plates do not (always) contain country codes, you'd need multiple keys, that are only locally unique. That said, I agree you should name those keys appropriately, e. g. LUID (as opposed to GUID). :cool:
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
we are not talking user defined fields but the internal unique key assigned to a record, PKid in the vernacular, a system defined seeded auto incrementing Int and yet you could still end up with duplicates
You cant outrun the world, but there is no harm in getting a head start Real stupidity beats artificial intelligence every time.
-
we are not talking user defined fields but the internal unique key assigned to a record, PKid in the vernacular, a system defined seeded auto incrementing Int and yet you could still end up with duplicates
You cant outrun the world, but there is no harm in getting a head start Real stupidity beats artificial intelligence every time.
Ouch, I see your point. Reminds me: "How can you trust a man that wears both a belt and suspenders? Man can't even trust his own pants." (Once upon a Time in the west)
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
-
Even the VB category is mostly for VB.Net not for VB6. I can understand that VB6 is over a decade old and everyone thinks it's old hat, but Access keeps on going with more releases every so often. As far as I know the latest version is MSAccess 2013. It's viable and I have written some programs for myself and others that we can't live without. So come on guys. Give us desktop database managers a place. Have a heart!