Return-Path: Delivered-To: apmail-jakarta-poi-user-archive@www.apache.org Received: (qmail 23823 invoked from network); 9 Jun 2006 14:29:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Jun 2006 14:29:29 -0000 Received: (qmail 85465 invoked by uid 500); 9 Jun 2006 14:29:27 -0000 Delivered-To: apmail-jakarta-poi-user-archive@jakarta.apache.org Received: (qmail 85438 invoked by uid 500); 9 Jun 2006 14:29:26 -0000 Mailing-List: contact poi-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "POI Users List" Reply-To: "POI Users List" Delivered-To: mailing list poi-user@jakarta.apache.org Received: (qmail 85427 invoked by uid 99); 9 Jun 2006 14:29:26 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Jun 2006 07:29:26 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=HTML_MESSAGE,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of karthik.kumar@bankofamerica.com designates 171.161.160.80 as permitted sender) Received: from [171.161.160.80] (HELO txdmzmailmx04.bankofamerica.com) (171.161.160.80) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Jun 2006 07:29:24 -0700 Received: from txdmzmailmx01.bankofamerica.com ([171.182.168.78]) by txdmzmailmx04.bankofamerica.com (8.13.6/8.13.6) with ESMTP id k59ET34V001709 for ; Fri, 9 Jun 2006 14:29:03 GMT Received: from memscmpl1. (memscmpl1-171178000202.bankofamerica.com [171.178.0.202]) by txdmzmailmx01.bankofamerica.com (8.13.6/8.13.6) with SMTP id k59ESXkS008135 for ; Fri, 9 Jun 2006 14:29:03 GMT Received: from memmta0101 (171.186.236.137) by memscmpl1. (Sigaba Gateway v3.90) with ESMTP id 329133326; Fri, 09 Jun 2006 14:29:02 +0000 Date: Fri, 09 Jun 2006 10:28:56 -0400 From: "Kumar, Karthik" Subject: Qn regarding HSSFDataFormat To: POI Users List Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.5 Content-type: multipart/alternative; boundary="Boundary_(ID_94mm5AYZ53tl89/KXMxQTw)" Content-class: urn:content-classes:message Thread-topic: Qn regarding HSSFDataFormat Thread-index: AcaL0QprdDNvHLuEShOGpypj34ZgSQ== X-MS-Has-Attach: X-MS-TNEF-Correlator: X-OriginalArrivalTime: 09 Jun 2006 14:28:59.0470 (UTC) FILETIME=[0C233EE0:01C68BD1] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --Boundary_(ID_94mm5AYZ53tl89/KXMxQTw) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Why does the HSSFDataFormat define a bunch of predefined formats? Isn't this less flexible than the Java way of doing it (SimpleDateFormat for example), where you can construct your own format string? I need to define my own format string in HSSFDataFormat. The javadoc shows this: "Utility to identify builin formats. Now can handle user defined data formats also. The following is a list of the formats as returned by this class." It says it can handle user defined data formats also. But the javadoc for this class is terrible. Nowhere does it say *how* this can be done. Does anyone know how to do this? Karthik Kumar Contractor MBS/ABS Analytics Banc of America Securities, LLC (704) 683-5188 --Boundary_(ID_94mm5AYZ53tl89/KXMxQTw)--