|
C&P Data
Dictionary: RETAINERS |
Other files:
acc_periods
access_privs
accounts
addresses
ap
ar
ar_items
archived_jobs
asset_types
asset_files
asset_prefs
avail
billing_info
cal
calendar
change_items
change_order
checks
check_items
clients
contacts
costs
credit_card_prefs
date_count
depts
est_revs
f_preference
finance
global_vars
groups
history
history_client
history_vendor
home
int_items
je
jobs
job_order
job_task
job_types
media_briefs
media_est
media_est_items
media_items
media_plans
media_prefs
meetings
mlink
mlink_prefs
odbcusers
outbox
palm_cats
palm_jobs
palm_tasks
payments
payment_items
pc
pictures
po_items
po_template
prefs
print_specs
programs
projects
proposals
purchase_order
rates
recur_ap
retainers
sales_actions
sales_campaigns
sales_letters
schedule_chart
schedule_header
staff
statements
stations
status_codes
sub_classes
task_table
temp_tasks
thought
time_import
timecard
timeline
user_info
vendors
version
web_html
web_ip_log
web_log
web_prefs
web_users_log
working
worksheets
y1099
|
RETAINERS is
the data file that stores the Client Retainer Schedule. Each RETAINERS
record contains a Client Retainer Schedule for the current year.
It is a lookup file used primarly on Retainer Billings. Each RETAINER
record has fields for RETAINER Ammount (i.e., RET_AMT1 through
RET_AMT12), Status (i.e., RET_1_OK through RET_12_OK), and Retainer
Date and Invoice Number (i.e., RET_DATE1 through RET_DATE12 and
RET_AR_NUM1 through RET_AR_NUM12) for each Retainer Schedule.
See related data
files: CLIENTS AR
Field
Name: |
Type: |
Length: |
Index: |
Description: |
RET_CLIENT_NUM |
char |
10 |
x |
|
RET_AMT1 |
number |
2dp |
|
|
RET_AMT2 |
number |
2dp |
|
|
RET_AMT3 |
number |
2dp |
|
|
RET_AMT4 |
number |
2dp |
|
|
RET_AMT5 |
number |
2dp |
|
|
RET_AMT6 |
number |
2dp |
|
|
RET_AMT7 |
number |
2dp |
|
|
RET_AMT8 |
number |
2dp |
|
|
RET_AMT9 |
number |
2dp |
|
|
RET_AMT10 |
number |
2dp |
|
|
RET_AMT11 |
number |
2dp |
|
|
RET_AMT12 |
number |
2dp |
|
|
RET_1 |
char |
40 |
|
|
RET_2 |
char |
40 |
|
|
RET_3 |
char |
40 |
|
|
RET_4 |
char |
40 |
|
|
RET_5 |
char |
40 |
|
|
RET_6 |
char |
40 |
|
|
RET_7 |
char |
40 |
|
|
RET_8 |
char |
40 |
|
|
RET_9 |
char |
40 |
|
|
RET_10 |
char |
40 |
|
|
RET_11 |
char |
40 |
|
|
RET_12 |
char |
40 |
|
|
RET_1_OK |
integer |
(0-255) |
|
|
RET_2_OK |
integer |
(0-255) |
|
|
RET_3_OK |
integer |
(0-255) |
|
|
RET_4_OK |
integer |
(0-255) |
|
|
RET_5_OK |
integer |
(0-255) |
|
|
RET_6_OK |
integer |
(0-255) |
|
|
RET_7_OK |
integer |
(0-255) |
|
|
RET_8_OK |
integer |
(0-255) |
|
|
RET_9_OK |
integer |
(0-255) |
|
|
RET_10_OK |
integer |
(0-255) |
|
|
RET_11_OK |
integer |
(0-255) |
|
|
RET_12_OK |
integer |
(0-255) |
|
|
RET_DATE1 |
date |
1980..2079 |
|
|
RET_DATE2 |
date |
1980..2079 |
|
|
RET_DATE3 |
date |
1980..2079 |
|
|
RET_DATE4 |
date |
1980..2079 |
|
|
RET_DATE5 |
date |
1980..2079 |
|
|
RET_DATE6 |
date |
1980..2079 |
|
|
RET_DATE7 |
date |
1980..2079 |
|
|
RET_DATE8 |
date |
1980..2079 |
|
|
RET_DATE9 |
date |
1980..2079 |
|
|
RET_DATE10 |
date |
1980..2079 |
|
|
RET_DATE11 |
date |
1980..2079 |
|
|
RET_DATE12 |
date |
1980..2079 |
|
|
RET_AR_NUM1 |
char |
10 |
|
|
RET_AR_NUM2 |
char |
10 |
|
|
RET_AR_NUM3 |
char |
10 |
|
|
RET_AR_NUM4 |
char |
10 |
|
|
RET_AR_NUM5 |
char |
10 |
|
|
RET_AR_NUM6 |
char |
10 |
|
|
RET_AR_NUM7 |
char |
10 |
|
|
RET_AR_NUM8 |
char |
10 |
|
|
RET_AR_NUM9 |
char |
10 |
|
|
RET_AR_NUM10 |
char |
10 |
|
|
RET_AR_NUM11 |
char |
10 |
|
|
RET_AR_NUM12 |
char |
10 |
|
|
LEGEND:
Type indicates whether a field contains characters (i.e., "char")
which contains any combination of letters or numbers, numbers (which
has a set number of decimal places), or integers (i.e., numbers
that range from 0 to 255 only).
Length shows the size of a field. Character fields have lengths that
are fixed, depending on their purpose. Description and note fields have
a length of 32000, which make them variable-length; their actual size depends
on how much data is entered into them.
Index indicates fields that are indexed in the database, which makes
them key fields for finding and sorting data. For best performances on
reporting and exporting, searches should made on index fields first.
Need
help exporting? See the Exporting
Data from Clients & Profits tech note.
|
|
|
| © Clients & Profits, Inc. w
e l o v e a d v e r t i s i n g |
|
|
