Oh fer gawd's sake... I'm such a tard.
There's nothing wrong with BD_SetIntegerColumn(). The problem was between the back of my chair and the keyboard.
"SELECT NAME FROM PROFILES" as a dataset does NOT mean that I can update anything other than NAME. But I didn't even bother checking my dataset to make sure I had the correct set chosen. "SELECT * FROM PROFILES" (after rebuilding the dll about 2903428475394 times) in the blitz program and it works just fine.
Having said that... I will be adding a "debug" mode to the dll so that if an error occurs in the future it will pop up a messagebox showing the actual ADO error that caused the problem. This should help debugging go a lot smoother.
To recap... No bug. It worky just fine! Expect RC5 tonight or tomorrow with debug mode included.
Kanati
There's nothing wrong with BD_SetIntegerColumn(). The problem was between the back of my chair and the keyboard.
"SELECT NAME FROM PROFILES" as a dataset does NOT mean that I can update anything other than NAME. But I didn't even bother checking my dataset to make sure I had the correct set chosen. "SELECT * FROM PROFILES" (after rebuilding the dll about 2903428475394 times) in the blitz program and it works just fine.
Having said that... I will be adding a "debug" mode to the dll so that if an error occurs in the future it will pop up a messagebox showing the actual ADO error that caused the problem. This should help debugging go a lot smoother.
To recap... No bug. It worky just fine! Expect RC5 tonight or tomorrow with debug mode included.
Kanati