29-03-2010, 03:38 PM
There is a bug in FSP or in the export function regarding time formats. It seems as though times are recorded in whole
numbers of seconds. When using FSP in stand alone mode, this doesnt seem to be a problem. However when exporting any flight
details this does become a problem. The problem reults in an SQL error when attempting to insert any values into a field
with an attriubute of TIME. If the value to be inserted has a value where the last 2 digits are 60 or less (eg a minute or
less), the insert will complete without errors. If however the last two digits are greater than 60 (more than a whole
minute) an SQL error is thrown, indicating an incorrect TIME value.
see the example below:
360 = 6 whole minutes - This will insert without errors
361= 6 min. 1 sec. - This will throw an SQL error
245 = No errors
275 = Errors
The attribute for an affected feild can be changed to TEXT, but this then causes formatting issues with any time data being
output.
Is there a proper fix for this?
numbers of seconds. When using FSP in stand alone mode, this doesnt seem to be a problem. However when exporting any flight
details this does become a problem. The problem reults in an SQL error when attempting to insert any values into a field
with an attriubute of TIME. If the value to be inserted has a value where the last 2 digits are 60 or less (eg a minute or
less), the insert will complete without errors. If however the last two digits are greater than 60 (more than a whole
minute) an SQL error is thrown, indicating an incorrect TIME value.
see the example below:
360 = 6 whole minutes - This will insert without errors
361= 6 min. 1 sec. - This will throw an SQL error
245 = No errors
275 = Errors
The attribute for an affected feild can be changed to TEXT, but this then causes formatting issues with any time data being
output.
Is there a proper fix for this?
![[-]](http://www.fspassengers.com/forum/images/collapse.png)