Knowledge Base
Knowledge Base
Knowledge Base
Knowledge Base
| Home | RDP Sales | Contact Us | Training |
|
| RDP Support | ||||
|
RDPWin Knowledge Base |
RDP-DOS Knowledge Base |
IRM and IRM.Net Knowledge Base |
Crystal Knowledge Base |
|
Added 12/26/02 - Article ID#: K000132
The credit limit for a reservation is established at check-in. The credit limit amount is stored on the second page of the reservation in field 63.
The default credit limit
for a CASH only reservation is $1000. The default credit limit for a
reservation with a credit card on file is also $1000. To change these defaults,
follow the steps below:
1.
From the System Manager Menu, choose option "090" -
"Update System Tables".
2. Choose option "U" - "Update System Tables".
3. Enter table number "C1".
4.
Enter "S" to add/change a sub-record. The sub-record is CRLIM1.
This is the default credit limit for guests with a credit card on their
reservation. A dollar amount can
either be entered in field #1, or the word "PROMPT".
With "PROMPT", the following appears at check-in.
5. Add another sub-record, CRLIM2. Sub-record CRLIM2 is the default credit limit for cash paying customers (designated by a blank credit card field). Most properties set this sub-record to $0.00.
Once the credit limit has been set on a reservation, it may be updated by changing field 63 on the reservation. Typically the Guests Over Credit Limit Report (#756) from the night audit reports menu is run as part of the night audit. Those guests that have exceeded their credit limit are noted and their credit cards are incrementally authorized for the difference. Credit card authorizations taken using the SDC module will automatically update the credit limit field.
Note: Payments do not change the credit limit.
| Supported Environments as of10/15/08 See Hardware Requirements for an entire list. |
|
|---|---|
| Workstations | All workstations must use either Windows XP Professional or Windows Vista (Business or Ultimate) 32-bit only (not 64 bit on workstations) with all service packs installed . RDP no longer supports Windows 95, 98, ME, or 2000 Workstations. For RDPWin, a minimum of 1 GB of RAM and a dual core processor or faster are required. See Hardware Requirements for an entire list. |
| Servers | The data server must be Windows 2003 or 2008 32 or 64 bit with all service packs installed and at least 4GB of RAM (16 for customers with 20 or more workstations). RDP no longer supports Novell Netware Servers. Feel free to call RDP Support at 970- 845-7108 with any hardware questions. |
| Pervasive | The Pervasive database must be Version 9.52 or higher with all Service Packs installed. See Pervasive Overview. |
| Printing Issues | RDPWin supports all standard Windows Printing environments. Our legacy RDP-DOS system may not be able to print if the printer is USB, TCP/IP or wireless. Additionally, printing remotely with Terminal Services or Citrix may not work with RDP-DOS. |
| NetMeeting or Remote Desktop |
To provide the highest level of support, RDP requires access to your system with Remote Desktop or Microsoft NetMeeting. Carbon Copy and other remote tools are not supported. See Hardware Requirements for more details. |
| RDPWin | RDPWin is our Microsoft .Net Windows-based software. It accesses the same database at the same time as your existing RDP-DOS and Internet Reservation Module (IRM). Please review: |
| For more information see Hardware Requirements. | |
| Home | RDPWin | RDP-DOS | IRM/IRM.Net | Open A Web Support Ticket |
|---|---|---|---|---|
|
Version 2.xxx | Upgrade to RDPWin | Link to Marketing Site | Contact Us |
| Training | Vendor Interfaces | Troubleshooting | RDP Sales Website |