You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Found this by chance via a non-initialised double. During debug, the double val was getting a value of 1.47787484E+300. Intersting the RDBMS didn't complain when this value was posted. BUT, access to the record that has this value later and i find i'm unable to open a transaction. Hope this is of use. cheers, nsm
Update: I think this bug may be related to droping a table and re-creating a modified form, all within the same transaction, as i was getting the db corruption with the following error message Partner index description not found (175)). I suspect that the bug above is a result of this programatic drop/restore action.
The text was updated successfully, but these errors were encountered:
description: Hi,
Found this by chance via a non-initialised double. During debug, the double val was getting a value of 1.47787484E+300. Intersting the RDBMS didn't complain when this value was posted. BUT, access to the record that has this value later and i find i'm unable to open a transaction. Hope this is of use. cheers, nsm
=>
Hi,
Found this by chance via a non-initialised double. During debug, the double val was getting a value of 1.47787484E+300. Intersting the RDBMS didn't complain when this value was posted. BUT, access to the record that has this value later and i find i'm unable to open a transaction. Hope this is of use. cheers, nsm
Update: I think this bug may be related to droping a table and re-creating a modified form, all within the same transaction, as i was getting the db corruption with the following error message Partner index description not found (175)). I suspect that the bug above is a result of this programatic drop/restore action.
Submitted by: nile mosley (nile_metriq.biz)
Hi,
Found this by chance via a non-initialised double. During debug, the double val was getting a value of 1.47787484E+300. Intersting the RDBMS didn't complain when this value was posted. BUT, access to the record that has this value later and i find i'm unable to open a transaction. Hope this is of use. cheers, nsm
Update: I think this bug may be related to droping a table and re-creating a modified form, all within the same transaction, as i was getting the db corruption with the following error message Partner index description not found (175)). I suspect that the bug above is a result of this programatic drop/restore action.
The text was updated successfully, but these errors were encountered: