Client:

I$\text{'}$m trying to understand how all this will work. What keeps a customer from going into the app and adding loyalty points themselves?

You:

Each user, whether a customer or employee, is given access only to perform the tasks they need to perform. So while a manager can

Select

a customer's account to add or remove loyalty points, the customer can only read that information.

Client:

What happens if a manager at the store is making changes on the same account that a customer service rep over the phone is also working on$?$ Could a customer end up with double the amount of credit adjustment?

You:

This is unlikely. We'll incorporate a technique called

Select

to ensure that only one person can make changes to an account at a time.

Client:

I've heard that designing queries can be pretty complicated, but I want to be able to pull up information myself without needing help from a programmer. Is that possible?

You:

Yes$$we can use a DBMS that supports

Select

so you can use a visual interface to design your own queries.

You$$re designing a relational database for a customer loyalty app you$$re developing for a client. The client has been saving information in a series of Excel spreadsheets, but the volume of data is becoming too unwieldy to use spreadsheets effectively. Before you can import the data from the client$$s existing records, you need to set up some relationships between tables in the database.