[AccessD] Re: Export to CSV file problem

This is really simple guys/gals:

Parse the date out and rebuild it in a query, add a field:

Date: cstr(datepart("m",YourDateField) & "/" &
       datepart("d",YourDateField) & "/" &
       datepart("yyyy",YourDateField))

Like someone else pointed out, you did not solve your problem,
you only put a Band-Aid on it.

Naming things in your database poorly because someone else did
in theirs is just an excuse.  As shown above, you can name a
column in a query anything you want and yours still be named
properly. Then you can use your transfertext on the query.  And,
since I used the cstr function, it really is a string.

Robert

At 10:06 AM 10/26/2004 -0500, you wrote:
>Date: Tue, 26 Oct 2004 07:19:37 -0500
>From: "Kaup, Chester A" <kaupca at chevrontexaco.com>
>Subject: RE: [AccessD] Export to CSV file problem
>To: "Access Developers discussion and problem solving"
>         <accessd at databaseadvisors.com>
>Message-ID:
> 
><1375769556091B4DAABC159F944CA1BB07A267 at bocnte2k4.hou150.chevrontexaco.net>
>
>Content-Type: text/plain; charset=us-ascii
>
>The field in the table is text. I tried date/time and both the date and
>the time displayed in the table. The export is dome by the transfertext
>method. The reason I used the word date is because the csv file
>generated is loaded into another program where the field names need to
>match and the field name in that program is date. I solved the problem
>by making the date field nine characters. Maybe not the best way but it
>chops of the time part of date/time and shows only the date in the csv
>file.
>
>Chester Kaup
>Information Management Technician
>IT-MidContinent/MidContinent Business Unit
>CTN 8-687-7415
>Outside 432-687-7415