Sponsored Content
Special Forums UNIX and Linux Applications Virtualization and Cloud Computing Mini Review: SliceHost v. Linode Customer Service Post 302376134 by Phlak on Monday 30th of November 2009 05:36:06 PM
Old 11-30-2009
Just call your bank and have them reverse the credit card transactions. They usually only require proof that you have attempted to contact the company, and an email will usually cover that. Plus, by reversing this fee, the company is usually charged for a credit card reversal, you can call that getting even.

On the note of SliceHost... I've had a single 512 Slice with them for several months now (6-8?), and love them. Everything you've stated I have also found to be true. Their service is great, customer service is helpful and they are extremely transparent about everything they do.
 

3 More Discussions You Might Find Interesting

1. HP-UX

Customer support engineer

Hi All, I need the help to deploy or implement HP MC service guard 2 node cluster step by step procedure is any1 who can help me to send me the step by step procedure. Thanks and Regards Jahangir (12 Replies)
Discussion started by: Jahangir
12 Replies

2. Virtualization and Cloud Computing

Mini Review: SliceHost v. Linode Ubuntu 9.10 Setup

October 2010 Update: Linode Versus Slicehost – One Year Later A few days ago I posted Mini Review: SliceHost v. Linode Customer Service. At that time, I was going to cancel my account with Linode based on problems during the sign-up period. However, Linode asked me to give them another... (2 Replies)
Discussion started by: Neo
2 Replies

3. Android

Mini Review: Samsung Galaxy S (Android 2.1) v. Nokia E63

Well, I've had my new Galaxy S around one day now and I must say, I am not sure if I regret buying it or not. Before buying it, I read a lot of reviews about the Galaxy S (e.g. Samsung I9000 Galaxy S review: From outer space), including reviews of problems with the GPS and some intermittent WiFi... (6 Replies)
Discussion started by: Neo
6 Replies
LedgerSMB::AA(3pm)					User Contributed Perl Documentation					LedgerSMB::AA(3pm)

NAME
LedgerSMB::AA - Contains the routines for managing AR and AP transactions. SYNOPSIS
This module contains the routines for managing AR and AP transactions and many of the reorts (a few others are found in LedgerSMB::RP.pm). All routines require $form->{dbh} to be set so that database actions can be performed. This module is due to be deprecated for active development as soon as a replacement is available. post_transaction() Post transaction uses the following variables in the $form variable: * dbh - the database connection handle * currency - The current users' currency * defaultcurrency - The "normal" currency * department - Unknown * department_id - ID for the department * exchangerate - Conversion between currency and defaultcurrency * invnumber - invoice number * reverse - ? * rowcount - Number of rows in the invoice * taxaccounts - Apply taxes? * taxincluded - ? * transdate - Date of the transaction * vc - Vendor or customer - determines transaction type get_files Returns a list of files associated with the existing transaction. This is provisional, and will change for 1.4 as the GL transaction functionality is {ref_key => $self->{id}, file_class => 1} rewritten delete_transaction(\%myconfig, $form) Deletes a transaction identified by $form->{id}, whether it is an ar or ap transaction is identified by $form->{vc}. $form->{invnumber} used for the audittrail routine. transactions(\%myconfig, $form) Generates the transaction and outstanding reports. Form variables used in this function are: approved: whether or not transactions must be approved to show up transdatefrom: Earliest day of transactions transdateto: Latest day of transactions month, year, interval: Used in palce of transdatefrom and transdate to vc: 'customer' for ar, 'vendor' for ap. meta_number: customer/vendor number entity_id: A specific entity id parts_id: Show transactions including a specific part department_id: Transactions for a department entity_credit_account: As an alternate for meta_number to identify a customer of vendor credit account invoice_type: 3 for on-hold, 2 for active The transaction list is stored at: @{$form->{transactions}} get_name(\%myconfig, $form) Retrieves the last account used. Also retrieves tax accounts, departments, and a few other things. Form variables used: vc: customer or vendor ${vc}_id: id of vendor/customemr transdate: Transaction date desired Sets the following form variables currency exchangerate forex taxaccounts taxform_exist($form, $cv_id) Determines if a taxform attached to the entity_credit_account record (where the id field is the same as $cv_id) exists. Returns true if it exists, false if not. update_ac_tax_form($form,$dbh,$entry_id,$report) Updates the ac_tax_form checkbox for the acc_trans.entry_id (where it is the same as $entry_id). If $report is true, sets it to true, if false, sets it to false. $report must be a valid *postgresql* bool value (0/1, t/f, 'true'/'false'). get_taxchech($entry_id,$dbh) Returns true if the acc_trans record has been set to reportable in the past false otherwise. save_intnotes($form) Saves the $form->{intnotes} into the ar/ap.intnotes field. COPTYRIGHT
# LedgerSMB # Small Medium Business Accounting software # http://www.ledgersmb.org/ # Copyright (C) 2006-2010 # This work contains copyrighted information from a number of sources all used # with permission. # # This file contains source code included with or based on SQL-Ledger which # is Copyright Dieter Simader and DWS Systems Inc. 2000-2005 and licensed # under the GNU General Public License version 2 or, at your option, any later # version. For a full list including contact information of contributors, # maintainers, and copyright holders, see the CONTRIBUTORS file. # # Original Copyright Notice from SQL-Ledger 2.6.17 (before the fork): # Copyright (C) 2006 # # Author: DWS Systems Inc. # Web: http://www.sql-ledger.org # # Contributors: # # # See COPYRIGHT file for copyright information perl v5.14.2 2012-03-26 LedgerSMB::AA(3pm)
All times are GMT -4. The time now is 11:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy