|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||||||
|
|||||||||||||||||
|
|||||||||||||||||
|
|||||||||||||||||
|
|||||||||||||||||
|
|
||||||||
|
|||||||||
|
|
|
|
Company
|
|
 SQL LINKS DEVELOPER SUPPORT
SEARCH Borland Online/Developer Support
Subject: MS SQL DateTime Conversion - Datapump Customer figured out what the problem was by the time I called him. The machine he was doing this on was configured for French-Canadian date format, where the proper abbreviation for months includes a period (e.g. Sept.) but the server was apparently not configured for this, so it rejected the date. It works if he changes the machine's configuration to Canadian-English. Now he says all he has to to is figure out how to get the server to accept French-Canadian formatted dates. >>>11/01/96 08:10am >>> He's having problems moving a .db table with a DateTime field into MS-SQL 6.5; gets DateTime conversion error using batchmove() or migration tool (DataPump). I found the following tidbit on dexter: Problem: DateTime Column Problems These problems manifest themselves in different ways. One of them is an error message "Conversion of char to DateTime resulted in a datetime value out of range." To correct this make sure that the DBLibrary - W3DBLIB.DLL - is dated 9-17-93. Or, simply try one until it works. There are many different sources for this file. PUB MSSQL DMW ERROR SW
|
|
||
|
|
|
|||
|
|||||
|
|
||||
 |
|||||
|
|||||
| Made in Borland® Copyright© 1994-2003 Borland Software Corporation. All rights reserved. Report Piracy, Legal Notices, Privacy Policy Last Modified Monday, 26-Mar-2001 16:27:05 PST |
|||||
