![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
When i am importing a foxpro table, linked by ODBC, i have a problem with date field. The definition in foxpro is standard date. The program is from a third party, so everything is defined and we cannot change anything. We want to analyse a lot of data with crystal report in SQL server. While importing the record is refused with the error "insert error, column nn ('fieldname', DBTYPE-DBTIMESTAMP), status 6: Data overflow. Can somebody give me a solution? |
#3
| |||
| |||
|
|
Hi, This is reason of a null value data field in Foxpro table. Instead of column copy task, writes a script that checks if date is valid date (isDate() function in VB). And if not put null value, otherwise put original value. Tomasz B. "Wimtien" wrote: When i am importing a foxpro table, linked by ODBC, i have a problem with date field. The definition in foxpro is standard date. The program is from a third party, so everything is defined and we cannot change anything. We want to analyse a lot of data with crystal report in SQL server. While importing the record is refused with the error "insert error, column nn ('fieldname', DBTYPE-DBTIMESTAMP), status 6: Data overflow. Can somebody give me a solution? |
#4
| |||
| |||
|
|
When i am importing a foxpro table, linked by ODBC, i have a problem with date field. The definition in foxpro is standard date. The program is from a third party, so everything is defined and we cannot change anything. We want to analyse a lot of data with crystal report in SQL server. While importing the record is refused with the error "insert error, column nn ('fieldname', DBTYPE-DBTIMESTAMP), status 6: Data overflow. Can somebody give me a solution? |
#5
| |||
| |||
|
|
Hi Wimtien, You may be running into either of two problems: FoxPro and Visual FoxPro's earliest valid date is 1601-01-01 if your system date is set to Short or Long. Otherwise the earliest valid date is 0001-01-01. FoxPro and Visual FoxPro can have an "empty" date. Empty is not the same as Null. SQL Server has a lot of trouble dealing with this. -- Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP cindy_winegarden (AT) msn (DOT) com www.cindywinegarden.com "Wimtien" <Wimtien (AT) discussions (DOT) microsoft.com> wrote in message news:42AC8785-A488-48CE-9236-B00AEA1472C1 (AT) microsoft (DOT) com... When i am importing a foxpro table, linked by ODBC, i have a problem with date field. The definition in foxpro is standard date. The program is from a third party, so everything is defined and we cannot change anything. We want to analyse a lot of data with crystal report in SQL server. While importing the record is refused with the error "insert error, column nn ('fieldname', DBTYPE-DBTIMESTAMP), status 6: Data overflow. Can somebody give me a solution? |
#6
| |||
| |||
|
|
Thanks Cindy The date is an "empty" date. Only i have to know now the sql convert function when i import the foxpro file into sql. If the foxpro-date is empty than standard sql-date else foxpro-date. |
#7
| |||
| |||
|
|
Hi Wintien, FoxPro has an Empty() function and you can also compare the value to {} which is the way to represent an empty date in a text string like an SQL command. -- Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP cindy_winegarden (AT) msn (DOT) com www.cindywinegarden.com "Wimtien" <Wimtien (AT) discussions (DOT) microsoft.com> wrote in message news:359A164E-88D7-4985-8EAC-B5F8E492561D (AT) microsoft (DOT) com... Thanks Cindy The date is an "empty" date. Only i have to know now the sql convert function when i import the foxpro file into sql. If the foxpro-date is empty than standard sql-date else foxpro-date. |
![]() |
| Thread Tools | |
| Display Modes | |
| |