Redundent data

SALAH@SAAD

New member
Local time
Tomorrow, 01:41
Joined
Nov 7, 2024
Messages
1
I work on Access form when I try to retrieve a value from a table field to my form combobox the data shown is randum
I used thismethod:
Dim my table
Set my table
Me.field = table!field
Is it necessary to declare the pk and how
 
Welcome to Access World! We're so happy to have you join us as a member of our community. As the most active Microsoft Access discussion forum on the internet, with posts dating back more than 20 years, we have a wealth of knowledge and experience to share with you.

We're a friendly and helpful community, so don't hesitate to ask any questions you have or share your own experiences with Access. We're here to support you and help you get the most out of this powerful database program.

To get started, we recommend reading the post linked below. It contains important information for all new users of the forum:

https://www.access-programmers.co.uk/forums/threads/new-member-read-me-first.223250/

We hope you have a great time participating in the discussion and learning from other Access enthusiasts. We look forward to having you around!
 
Is it necessary to declare the pk and how
pk is Primary Key, the field on your table where there is No duplicate and Unique, just like everyone Social Number and Iqama number.
 
Is it necessary to declare the pk and how

Your issue is that tables aren't inherently sorted EVEN if they have a PK. It is a little-appreciated fact that most databases (including Access) are based on set theory, for which ordered / sorted data sets are not a requirement.

If you want something from your table to be presented in a specific order, create a query of that table and include an ORDER BY clause to sort whatever you wanted to appear in a particular order. Then use the query instead of the raw table.
 
pk is Primary Key, the field on your table where there is No duplicate and Unique, just like everyone Social Number and Iqama number.
I would amend that to acknowledge that, while identifiers like a Social "Number", Social Security "Number", and other similar identifiers are supposed to be unique, in reality, they may not be.

My ex-wife once worked in an office where part of her job involved tracking down duplicate SSNs on health insurance claims. It turns out that there is a black market for valid SSNs among the illegal aliens (now known as undocumented migrants) who needed such identifiers to qualify for benefits and obtain employment. This was more than 25 years ago, so I'm sure the problem is even greater now.

While that particular aspect of the problem lies at one end of the spectrum of potential problems, it does a great job of exposing the fallacy of relying on such government issued IDs to be unique.
 
About 15 years ago, my daughter also experienced a similar issue where her National Insurance number was duplicated for another person elsewhere in the UK. This led to her receiving a demand for unpaid tax.
In her case she was able to prove it was nothing to do with her. Whether it was due to fraud or computer error, I don't know
 
While that particular aspect of the problem lies at one end of the spectrum of potential problems, it does a great job of exposing the fallacy of relying on such government issued IDs to be unique.
Creating an application that used SSN and other similar types of "ID's" and using them as the PK has always been problematic and the SSA tells you to not use SSN as a PK.

The IRS is capable of identifying the misuse of SSN's but they choose not to in order to allow illegal aliens to work illegally using some other person's SSN. My brother is a victim of this type of fraud and has been fighting with the IRS for two years now because someone is reporting income using his SSN and they are trying to get him to pay back taxes. The fact that the criminal is reporting from a different state seems to be immaterial in their pea brains.
 

Users who are viewing this thread

Back
Top Bottom