is this design correct? and what fields to link

[Choksy]

Customer table

Customer ID (PK)
Customer name
Base

Authorisation details table

Auth ID (PK)
Name of authoriser
Power
Amount limit
Docs authorised

Account Details Table

Account ID (PK)
Account number (can be "no account", multiple account or single account)
If single or mutiple account then..

Account 1
Account 2
" " 6

Source Details table

Source ID (PK)
ID card and expiry date
Staut date
KBIS DATE
Expiry date
Process verbal date (can be more than one date)

 

[Mile-O]

Customer table: tblCustomers

CustomerID (PK)
CustomerForename
CustomerSurname
Base*

Authorisation details table: tblAuthorisations

AuthID (PK)
AuthoriserForename
AuthoriserSurname
Power *
LimitID (FK)
DocsAuthorised *

:Limit details table: tblLimits
LimitID[/b] (PK)
Limit

Accounts detail table: tblAccounts
AccountID (PK)
AccountNumber
CustomerID (FK)


I have no idea how the SOurce table fits into the design or how the authorisation table fits into the design either.


* No idea what this is. Is it dependant upon the primary key of the table?

 

[Choksy]

thanks for the reply.

Well.. forst of all a customer has a base number and this is unisque...and that base number can have no,one or several accounts. that base number represents the customer. With regards to authoriser table..

Each authoriser has different limits, say for example, one can have "no limit" and the other can have " 555 pounds" in the source table, the "ID Card" relates to the authoriser and his/her expiry date.

hope this helps

 

[Choksy]

further info

i think if i expalin the process it will help

OVERALL PROCESS

A customer sends details to the bank, such as base number, account no. and name of authorised signatories (people who are authorise to sign the documents on behalf of the company) to Citibank. Citibank then stores this information manually in files. However, if for any reason, the bank wants to request some documents from them, they have to search manually which is time consuming. This is where this system is helpful. So they can enter all the information details and update their records.

 

[Mile-O]

a base number and this is unisque (sic)...and that base number can have no,one (sic) or several accounts. that base number represents the customer. With regards to authoriser table

I still don't understand. If this field can be only one of three values then it is certainly not unique.

 

[Mile-O]

And the CustomerID should represent the customer; not this base number.

 

[Choksy]

wats d solution?

 

[Mile-O]

You know, we don't need this Account table (i.e. Single, Multiple, etc.

If you perform a count of the fields then if it's 1 then it's obviously a single account, if it's more than one then you have multiple accounts.


I still don't see how the Authoriser table relates...