×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
My boss built an SSIS pkg to connect to (hIT driver) and upload to the 400 into a work file that has the same layout as the production file.
I tried the date data type but it wasn't compatible with the date (L) or date/time stamp field (Z). Got an error when copying from the work file to the production file. Seemed to populate OK from the upload to the work file, though.
Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404
Receipt of this message does not grant you permission to send me
Unsolicited Commercial Email
"Alan Campin" <Alan.Campin@xxxxxxxxxxxxxxxx> 05/13/2008 3:49 PM >>>
<snip>
We are uploading data from our SQL server data base.
Our files all store the date 8/0 - the standard is no date data type.
The guys on the dotnet side tried to convert the SQLServer date data
type
column to 8/0 with no luck, so far.
I thought I'd change mine [entirely against our standards] and use the
date
data type.
This is what I see in our file using WRKDBF before a record is
populated:
0001-01-01-00.00.00.000000
This is what the server guys are trying to send:
2008-05-12
10:34:48.400 and no - between the date and time.
Any suggestions?
</snip>
You are not mentioning how you are receiving the data. Stored Procedure
call?
Just have your .net guys pass you a date data type but like I said
difficult to know unless we know how you are receiving the data.
midrange.com
