[Only registered and activated users can see links. Click Here To Register...]
[Only registered and activated users can see links. Click Here To Register...]
[Only registered and activated users can see links. Click Here To Register...]
help me pls. i have problem
02/25/2012 17:53
xdreakx#1
02/25/2012 18:09
[DEV]DorianGray#2
Brick Emigrator Message and Status Overflow Message is not the problem :D
The Bricks 101 102 103 104 105 are the bricks in the Siege Castle Map (Pendants or Gates,not sure)
The Last Error Message could be a Error in the Database or in the ODBC Settings in Windows.But i think it s a Database Error because varchar & datetime are Row options in a database table :-(
The Bricks 101 102 103 104 105 are the bricks in the Siege Castle Map (Pendants or Gates,not sure)
The Last Error Message could be a Error in the Database or in the ODBC Settings in Windows.But i think it s a Database Error because varchar & datetime are Row options in a database table :-(
02/25/2012 19:45
xdreakx#3
Quote:
The Last Error Message could be a Error in the Database or in the ODBC Settings in Windows.But i think it s a Database Error because varchar & datetime are Row options in a database table :-(
how I can solve this problem?
02/26/2012 19:55
xdreakx#4
someone can help me solve the problem?
02/27/2012 08:12
freeskier4lif3#5
For the conversion error there is a very easy fix if you are using SQL 2008.
Just change your Siege scripts "datetime" variables to "date" variables and you won't get any out of range issues. The older "datetime" variable only accepts dates from January 1, 1753, through December 31, 9999. While the date variable accepts January 1, 1 A.D. through December 31, 9999 A.D.
You probably have something setup where you're getting a date out of range. So this should fix that error only.
Just change your Siege scripts "datetime" variables to "date" variables and you won't get any out of range issues. The older "datetime" variable only accepts dates from January 1, 1753, through December 31, 9999. While the date variable accepts January 1, 1 A.D. through December 31, 9999 A.D.
You probably have something setup where you're getting a date out of range. So this should fix that error only.