Results 1 to 3 of 3

Thread: Back to Euro date issue the other threads gone

  1. Jul 25th, 2002, 09:45 PM #1
    SoCalled
    SoCalled is offline

    Thread Starter
    Lively Member
    Join Date
    Jul 2002
    Location
    Planet Earth
    Posts
    99

    Question Back to Euro date issue the other threads gone

    The exact line of code is

    Code:
    objProduct.Purchase = #1/30/2001#
    Works , no problems


    if changed to

    Code:
    objProduct.Purchase = #30/1/2001#
    falls over. The date is in a variable, but hard coded to ensure this was what was happening...
    Reply With Quote Reply With Quote
  2. Jul 25th, 2002, 10:35 PM #2
    Sastraxi
    Sastraxi is offline
    Good Ol' Platypus Sastraxi's Avatar
    Join Date
    Jan 2000
    Location
    Ontario, Canada
    Posts
    5,134
    Well it's obvious it's in a set MM/DD/YYYY format. You can't just ask it to accept a DD/MM/YYYY format instead. Hence, there is no 30th month and that's why the code doesn't work.
    All contents of the above post that aren't somebody elses are mine, not the property of some media corporation.
    (Just a heads-up)
    Reply With Quote Reply With Quote
  3. Jul 25th, 2002, 10:41 PM #3
    SoCalled
    SoCalled is offline

    Thread Starter
    Lively Member
    Join Date
    Jul 2002
    Location
    Planet Earth
    Posts
    99
    Yeap realise that Sas...


    The computer is set to Australian date format which is Euro, the dates all work fine in vb5 and vb6 products, but don't work in vb.net. Is there an overriding setting in vs.net somewhere causing this.


    BTW the other four development products we use, all accept Euro date format, because it is used in the vast majority of countries around the world.
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules


Click Here to Expand Forum to Full Width