September 9, 2004 at 7:40 pm
this is probably not the right spot for this post but here goes....(as i am getting desparate)
We are using a software product that uses a paradox DB. The (USA) company has sent us a conversion program that sets up a SQL DB and converts the data into the tables. The program does not convert any of the records that have a date > the 12th day and reverses the day and the month of the records it does convert - 3r july in old is 07/03/2004 and in new 03/07/2004 (in both setups of programs I have the display date format as mm/dd/yyyy). I have checked the date format in syslanuages using
select dateformat
from syslanguages
where langid =
(select value from master..sysconfigures
where comment = 'default language')
and this displays m/d/y.
I sent my data to the US and the conversion works fine.
is there any other settings I can check on the server that will effect the date???
Brian
September 9, 2004 at 10:16 pm
So are you trying to make your SQL Server 'pretend' it is American? Don't know whether this will work, but you might try changing the control panel/regional options on the server.
Or perhaps the conversion program is assuming that your Paradox dates are already in US format and the SQL Server side is working absolutely fine?
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
September 9, 2004 at 10:30 pm
Seeing I could not get it to work the first time, I changed my regional settings to mm/dd/yy to see if this would make it work. All our servers are set with the sql default of m/d/y.
I am confused with the second part of your reply. The paradox Tables are on the server as well. The conversion program works in the US on our data but will not work on our server.
I am trying to eliminate environment issues on our end.
September 9, 2004 at 10:42 pm
So you've got everything you can find on your server set to US format and you're still getting d/m/y date format problems from somewhere?
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
September 9, 2004 at 10:56 pm
Yes, the coversion program (here) is not converting any of the dates with the day >12 ie it is treating this field as the month and therefore anything over 12 is invalid. However this is not occurring in the US. This is why I am having a lot of trouble convincing the support people that there is a problem, everything works fine on their system with our data.
Thats why I am thinking that it is my environment or possibly a sql statement that is in the conversion program that for some reason works differently outside of the US
September 9, 2004 at 11:06 pm
So do you know at what stage in the process that the conversion is failing for these records?
I'm thinking it could be
a) Something in the logic of the conversion program itself, or
b) When the data from the conversion program is passed to the SQL Server db - is it being rejected as invalid by SQL Server?
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
September 9, 2004 at 11:17 pm
Thats what I have been thinking. Unfortunately, the company will not give me the source code so that I can debug it (which is understandable). The confusing thing is that it works on their SQL server. I am in the hands of the creator.(of the software)
September 9, 2004 at 11:20 pm
Perhaps you could run Profiler to check the SQL Server side of the equation? Otherwise, I'm running out of ideas.
Good luck
Phil
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply