Re: SQL Casting/Exponential Notation -- MIDRANGE-L

Subject: Re: SQL Casting/Exponential Notation
From: John Yeung <gallium.arsenide@xxxxxxxxx>
Date: Thu, 17 May 2012 13:20:35 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Thu, May 17, 2012 at 12:54 PM, Michael Ryan <michaelrtr@xxxxxxxxx> wrote:

Sigh...yes, of course it's an Excel issue. Sorry for the post...I was
making expectations that I shouldn't have made. Thanks for the help.

No worries. Now, even though the case is closed on the culprit, there
is still the issue of what to do about it. Excel, for all its faults,
is a pretty good end-user application, and certainly an application
huge numbers of people are comfortable using. If this data is
normally going to be opened in Excel, it is probably worth it to
implement a way to deliver the data in a form that Excel won't mangle
(which is what I offered further help with, if needed).

John

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: SQL Casting/Exponential Notation , Michael Ryan

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.