RE: date format setting

Whistler,

Is there any rhyme or reason to which dates don't get imported correctly?

1. I recommend that you create a local Access table that you are going to
import the data into before exporting to Oracle. Define this date field as a
text field. This should make the import run better.

2. I also recommend that you create an import specification, and define
that date field as text. You do this using the File - Get External Data -
Import option. After you have identified the file to import, there is an
Advanced Option (don't forget to name and save the specification).

3. Once you have done this, you can use the cdate function to have Access
convert your "dd-mmm-yyyy" format into mm/dd/yyyy. Then, you can use the
Format( ) function to define the proper format for inserting into Oracle.

HTH
Dale

--
Don''t forget to rate the post if it was helpful!

email address is invalid
Please reply to newsgroup only.



"whistler" wrote:

Hi, I'm trying to accomplish through some VBA code:
read from a flat text file (fixed width) some information to be put in an Oracle table through ODBC.

Nothing special. But the text file has some "date fields" in the format "dd-mmm-yyyy", i.e. the 4th of March reads "04-MAR-2008. Some of the date values are however not correctly imported into the table, leaving the field in question blank after import is finished.

I am in the Netherlands, and I suspect that the problem comes from a difference in "date-format" setting between my MsAccess front end (version 2003) and the application that creates my input file. This latter being from another company's application, it is probably more straightforward to change my VBA code than to ask them to change their file layout.

Can somebody give me hint how to check and manipulate date format settings of my application to avoid the above problem ?

Thanks in advance,
Jos


--------------= Posted using GrabIt =----------------
------= Binary Usenet downloading made easy =---------
-= Get GrabIt for free from http://www.shemes.com/ =-


.

Relevant Pages

  • Re: Using Cursors
    ... > different than SQLServer in that they highly recommend not to use the ... > temp table solution when I code Oracle. ...
    (microsoft.public.sqlserver.programming)
  • Re: Using Cursors
    ... they involved too much memory and SQL server would crash. ... Using Oracle on the same machine, I have yet to run into a query that Oracle ... temp table approach doesn't scale very well; the DDL puts locks on the ... >> different than SQLServer in that they highly recommend not to use the ...
    (microsoft.public.sqlserver.programming)
  • Re: SQL Tuning Regarding System CPU Stats
    ... Since the system statistics are used per database ... that applications are what needs tuning, ... known book, published by O'Reilly few years ago, named "Optimizing Oracle ... I would recommend numerous available ...
    (comp.databases.oracle.server)
  • RE: Populate Access table with Oracle data - how?
    ... execute the SQL statement inside Access vs. Oracle. ... I ended up creating an XML parameter file that defined the export. ... > results in a local Access 2000 table for later use. ... I could open an ADO recordset and loop through ...
    (microsoft.public.data.ado)
  • Re: perl flawed or my fault
    ... Eric Schwartz wrote in comp.lang.perl.misc: ... I always recommend against the ?: ... with big complex branches. ... such a format can be found, there is no limit to the complexity. ...
    (comp.lang.perl.misc)