Solved Sales Database Relationships (1 Viewer)

You do not need these fields in tblCustomerPlatforms
CustomerUsrName
CustomerName
 
We don't know what you are selling so it is hard to know what makes sense but if you need to tie an invoke to the platform it came from, instead of CustomerID, you might need CustomerPlatformID in tblinvoices so you tie the invoice to the customer via the platform it came in on.

You DO need CustomerUserName in the Platform table. Each user can have a different ID depending on the platform. I think this got renamed as CustomerPLTID. So remove this field from customers and move it to platform.

Let's clarify again:
CustomerName is the real name of a person - too bad you didn't take my advice on breaking this up.
CustomerPLTID is the user name on a platform like mike60smart
Address is the customer's billing address - too bad you didn't take my advice on breaking this up.
Assuming that a phone is mobile caould cause a problem and not allowing for a non-mobile is short sighted. I personally never give my cell number to anyone unless I am meeting them somewhere. I never give it to companies and I always tell my friends who have the number not to call it unless we are on the way to meet. I simply refuse to be tied to a phone and the cell phone is for my convenience not anyone else
We don't know what you are selling so it is hard to know what makes sense but if you need to tie an invoke to the platform it came from, instead of CustomerID, you might need CustomerPlatformID in tblinvoices so you tie the invoice to the customer via the platform it came in on.

You DO need CustomerUserName in the Platform table. Each user can have a different ID depending on the platform. I think this got renamed as CustomerPLTID. So remove this field from customers and move it to platform.

Let's clarify again:
CustomerName is the real name of a person - too bad you didn't take my advice on breaking this up.
CustomerPLTID is the user name on a platform like mike60smart
Address is the customer's billing address - too bad you didn't take my advice on breaking this up.
Assuming that a phone is mobile caould cause a problem and not allowing for a non-mobile is short sighted. I personally never give my cell number to anyone unless I am meeting them somewhere. I never give it to companies and I always tell my friends who have the number not to call it unless we are on the way to meet. I simply refuse to be tied to a phone and the cell phone is for my convenience not anyone else's.
CustomerPLTID: Customer User Name in the relevant platform.
CustomerName: Now I have changed this into CustomerFirstName and CustomerLastName as per your suggestion. Also I detailed the address into AddressLine1 and AddressLine2, city and Province. Mobile is now Phone and Mobile.
 
As long as CustomerPLTID got moved from the customer table to the CustomerPlatforms table. That's fine but you didn't answer the question about whether or not the Invoice needed to link to the platform. If the user has two platform records, do you care which one he used to make the purchase?
Although we haven't encountered any such purachase yet, but hypothetically speaking if we did have, we're going to deal with the customer as another person and another account as if you have two accounts on ebay sharing same address and billing details.
 
I have re-defined the relationships. But couldn't figure out how data will be mapped between tblcustomers, tblcustomerplatforms and tblplatforms.
 

Attachments

  • 2021-10-24_22-31-23.jpg
    2021-10-24_22-31-23.jpg
    74.5 KB · Views: 177
Thanks to everyone who responded to this thread. The issue is now solved,
Special thanks to @mike60smart who helped me by redesigning the database.
 
The new Relationships are shown as follows:-
 

Attachments

  • RI.JPG
    RI.JPG
    54.1 KB · Views: 158

Users who are viewing this thread

Back
Top Bottom