SQLErrMsg() is always cut off... is it possible to see the full error message in the logs or something? (Why does Citect still insist on cutting characters to 256 in 2019??)
SQLErrMsg() is always cut off... is it possible to see the full error message in the logs or something? (Why does Citect still insist on cutting characters to 256 in 2019??)