Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP to SQL Import Errors
Message
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
01008543
Message ID:
01008611
Views:
15
The text of the error is:

"Error at destination for row number 157. Errors encountered so far in this task: 1.
Insert error, column 12('actdate', DBTYPE_DBTIMESTAMP), status 6: Data overflow.
Invalid character value for cast specification"

I went to record 157 and I don't see anything wrong.


Here is the text of the Insert CMD from the Transformations dialog:
CREATE TABLE [MCM].[dbo].[showtitl] (
[progtitl] char (20) NOT NULL, 
[clientid] char (4) NOT NULL, 
[active] bit NOT NULL, 
[untcst] numeric (7,2) NOT NULL, 
[upcst] numeric (7,2) NOT NULL, 
[upcst2] numeric (7,2) NOT NULL, 
[opprogtit] char (20) NOT NULL, 
[clprogtit] char (20) NOT NULL, 
[clprodid] char (20) NOT NULL, 
[cluser1] char (20) NOT NULL, 
[group] char (10) NOT NULL, 
[actdate] datetime NULL, 
[inactdate] datetime NULL, 
[upcst3] numeric (7,2) NOT NULL, 
[note] text NOT NULL, 
[progdesc] char (30) NOT NULL, 
[autophonen] bit NOT NULL, 
[rtimedmin] numeric (4,0) NOT NULL, 
[rtimedsec] numeric (3,0) NOT NULL, 
[rtime] numeric (7,0) NOT NULL, 
[rtimedesc] char (7) NOT NULL, 
[dubversion] char (15) NOT NULL, 
[td_id] char (10) NOT NULL, 
[budgetamt] numeric (8,0) NOT NULL, 
[prodcat] char (10) NOT NULL, 
[plprovided] bit NOT NULL, 
[modtstamp] numeric (10,0) NOT NULL, 
[cluntcst] numeric (7,2) NOT NULL, 
[clupcst] numeric (7,2) NOT NULL, 
[clupcst2] numeric (7,2) NOT NULL, 
[clupcst3] numeric (7,2) NOT NULL, 
[upcst4] numeric (7,2) NOT NULL, 
[upcst5] numeric (7,2) NOT NULL, 
[upcst6] numeric (7,2) NOT NULL, 
[upcst7] numeric (7,2) NOT NULL, 
[upcst8] numeric (7,2) NOT NULL, 
[upcst9] numeric (7,2) NOT NULL, 
[clupcst4] numeric (7,2) NOT NULL, 
[clupcst5] numeric (7,2) NOT NULL, 
[clupcst6] numeric (7,2) NOT NULL, 
[clupcst7] numeric (7,2) NOT NULL, 
[clupcst8] numeric (7,2) NOT NULL, 
[clupcst9] numeric (7,2) NOT NULL, 
[autophfirm] bit NOT NULL, 
[id] numeric (10,0) NOT NULL, 
[multibase] bit NOT NULL, 
[progtshort] char (10) NOT NULL, 
[campid] char (20) NOT NULL, 
[sourcetype] char (10) NOT NULL, 
[dubverenc] char (15) NOT NULL, 
[stype] char (2) NOT NULL, 
[altclid] char (4) NOT NULL, 
[traffnote] text NOT NULL, 
[upcst10] numeric (7,2) NOT NULL, 
[upcst11] numeric (7,2) NOT NULL, 
[upcst12] numeric (7,2) NOT NULL, 
[upcst13] numeric (7,2) NOT NULL, 
[upcst14] numeric (7,2) NOT NULL, 
[upcst15] numeric (7,2) NOT NULL, 
[upcst16] numeric (7,2) NOT NULL, 
[upcst17] numeric (7,2) NOT NULL, 
[upcst18] numeric (7,2) NOT NULL, 
[upcst19] numeric (7,2) NOT NULL, 
[upcst20] numeric (7,2) NOT NULL
)
>Try to change the column type to datetime.
>
>>They are still all in range
>>
>>>Oops, the range I provided was for datetime, For smaldatetime its January 1, 1900, through June 6, 2079.
>>>
>>>>The dates are all in range
>>>>
>>>>>The smalldatetime data type supports dates from January 1, 1753 and up. Check you data for dates that are out of range.
Everything makes sense in someone's mind
public class SystemCrasher :ICrashable
In addition, an integer field is not for irrational people
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform