Can U Help

connordrew

Registered User.
Local time
Today, 05:56
Joined
Aug 14, 2003
Messages
22
Hi there I was wondering if anyone could help me with my query.

I have been asked to design a database for a small call centre who take order by telephone via credit card. I have created the database with all the necessary contact and payment details etc and I have set the telephone number as the primary key.

When a customer calls in and gives their telephone number, the advisor would search the database and up will come the customer's details. But I want to be able to add the date and authorisation number of that transaction, without adding to the original database. For example, when the advisor gains an authorisation number for the credit card transaction, we want to capture that number to a new form maybe without adding to the original contact database. Also, can the date be added automatically as soon as the advisor inputs the authorisation code?

PS, I do not have any experience in VB or anything like that, I used the wizard and design view etc to create what I have already

I would be much appreciative of any help i this matter.

Thank-you




Can this be done.
 
Also, can the date be added automatically as soon as the advisor inputs the authorisation code?
Use the default value and put Date()
On creating a new record that will be filled.

if you dont want to add a new record (meaning one Phonenumber can only have 1 transaction, since your phonenumber is a primary Key) you can use the After update event of the Authorisation Code field and put in some VBA:
Me.YourDateField = Date()

If your farly new to Access and such i do suggest reading this

FAQ and these Tips

Regards
 
You're going to need two tables, one for the caller details and one for the transactions, otherwise, as namliam says, you will only ever be able to enter one transaction per contact.

Phone number is a poor choice as primary key for two obvious reasons. You can have two callers with the same phone number e.g. family members, flat shares, etc, so your PK would be duplicated. Secondly, people can change phone numbers. You don't need your primary key to change since this involves a huge amount of work. I would use an autonumber as PK. You can still search on the phone number, and index it, without it being the PK.
 

Users who are viewing this thread

Back
Top Bottom