I also discovered that CF_SQL_Numeric does not correspons to MS SQL Server
Numeric type, it is closer to an integer as it killed my decimal point
(rounds down to the closest integer).

CF_SQL_MONEY seams to work fine -- direct correspondance to MS SQL Money
type? (I think it is close enough)

I use CF_SQL_FLOAT for MS SQL Server types Real and Numeric - works OK.

cf_sql_longvarchar - does it work for MS SQL type 'text' ?

TK
  -----Original Message-----
  From: Bryan Stevenson [mailto:[EMAIL PROTECTED]
  Sent: Wednesday, October 22, 2003 2:34 PM
  To: CF-Talk
  Subject: Re: cfqueryparam

  and to add to that...you should really use cf_sql_integer for integers and
not cf_sql_numeric  (works either way...but would allow a decimal value when
it shouldn't) ;-)
    ----- Original Message -----
    From: Matt Robertson
    To: CF-Talk
    Sent: Wednesday, October 22, 2003 11:30 AM
    Subject: RE: cfqueryparam

    Tom wrote:
    >So far I am learning what works and what doesn't work
    >with our MS SQL server using trail and error.

    Been there and done that.  For what its worth, here's the result of my
    trial and error:  they'll work on Oracle, SQL Server, mySQL and Access
    with the exceptions noted below.

    cf_sql_varchar - all normal text types

    cf_sql_longvarchar - all 'long' text fields.  memo, clob etc.

    cf_sql_numeric - all numeric types.  Does not accept decimal values on
    SQL Server, for sure and maybe others

    cf_sql_decimal - See above.

    cf_sql_timestamp - date+time fields.  No Access date/time format works
    with any cfsqltype as far as I've been able to tell.

    I'd love to hear a fix for the Access date bit, as well as more
    documentation, anecdotal or otherwise.

    --------------------------------------------
    Matt Robertson       [EMAIL PROTECTED]
    MSB Designs, Inc.  http://mysecretbase.com
    --------------------------------------------


[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to