Seek source code examples of a "Call Center Form" 1

[HiBoo]

I'm trying to code a basic form that keeps track of calls received . I need to set up a database that tracks all the calls received so I can set up an automated call back system. I've already coded an "Organization" form to maintain the organizations I deal with. I seek some suggestions as how to best create a form to keep track of the calls coming in. I would prefer to have a form that allows me to quickly identify the caller by name and organization when regular contact is established. I currently have tables labeled ORGANIZATION(primary key - OrgID), CALLERS(primary key - ContactID, foreign key - OrgID) CALLS(primary key - CallID, foreign key - ContactID, EmpID), and EMPLOYEES(primary key - EmpID). Have I set a proper table structure? Any form suggestions would be great. Thanks.

 

[DougP]

Are you keying in these phone numbers or are they coming from a Caller ID system?

 

[HiBoo]

The phone numbers are being keyed. There is currently no automation. A call comes in and the information to be stored is keyed by the receiver of the call, an employee.

 

[DougP]

Ok<br>
So it depends on what you want to do on your form<br>
as to which table to attach it to.<br>
And if you want to find people (Employee's or Customers) and look up changing data in a subform such as Phone numbers etc.<br>
It can all be done but you need to decide when you pop up a form are you finding something and then creating a new instance or some other record.<br>
Or you can sketch out a form on paper (a Gee it would be nice if it did this) then it may be easier to figure out which tables connect to which objects on the form.<br>
Take it one step at a time<br>
Don't try to start several items at once hoping to figure out how to make them work later.<br>
Example<br>
1. When a call is received employee clicks a certain form.<br>
2. Adds a new record (date & time can be inserted automatically with a AddNew Rec button in the VBA code.<br>
3. Key in phone number and other data.<br>
4. Click Update or close<br>
<br>
Repeat for next call<br>
<br>
Now then the call back procedure. is the PC going to intiate the call and some emplyee will pick it up.<br>
Or are you wanting to print a list and hand it to the employee to call?<br>
<br>
<br>
DougP<br>
<br>

 

[HiBoo]

Call Back:<br>
<br>
An employee is to print a list. The &quot;Calls&quot; table has a &quot;Bring Forward Date&quot; attribute. The report is to automatically print upon opening each morning with all &quot;Bring Forward Date&quot; attributes equalling the current date.

 

[DougP]

Well to automate the report<br>
you can have an Icon on the desktop with the following in Properties<br>
<br>
&quot;C:\Microsoft Office97\Office\MSACCESS.EXE&quot; P:\Stocks\RollingStockPlanner.mdb /X LetMeSeeIt<br>
<br>
1. Microsoft Access and it's path <br>
2. Blank Space<br>
3. Database and its path<br>
4. Blank Space<br>
5. /X Macro name<br>
Macro name canot have an spaces in it.<br>
i.e. LetMeSeeIt in our example<br>
<br>
Create a macro in Access that opens the report <br>
the macro name of course without spaces is what is put in the icon.<br>
the reports date for today is<br>
=format(now,&quot;mm/dd/yy&quot <br>
Put this in the date field on the report or where ever you want today's date.<br>
<br>
Now you can put an Icon in the Startup group of the machine to print the report each morning.<br>
So when the machine boots it will print the report.<br>
But everytime it reboots it will print the report too.<br>
<br>
hope this helps

 

[HiBoo]

To DougP,<br>
<br>
Thank you so much for your assistance. I'll give it a shot. I think it will work out great that way.

 

[elizabeth]

If you create the form based on the Calls table DougP suggested, you can make each of the controls a combobox with the &quot;LimitToList&quot; (data) property set to&quot;No&quot;. Then add code to the &quot;OnNotOnList&quot; event similar to this:<br>
<br>
Dim intAnswer As Integer<br>
intAnswer = MsgBox(&quot;Caller not in table. Edit tblCaller?&quot;, vbYesNo, vbQuestion)<br>
If intAnswer = vbYes Then<br>
DoCmd.OpenForm &quot;frmCaller&quot;, acNormal, , , acFormEdit, acDialog <br>
Response = acDataErrAdded<br>
Else<br>
Response = acDataErrContinue<br>
End If<br>
End Sub<br>
<br>
The code opens a form with all the existing values each time the user keys a value that is not in the table. The form allows edits and adds. You would want to use this same methodology (combobox with AddToList not allowed, and this code on the OnNotOnList event) in all your forms for the foreign keys.