06.10.2026, 14:53
In Claude written database - should not call DIALOG END CBHNDL under %WM_CLOSE, because it actually causes the program to crash-stop in a loop of WM_CLOSE calls where it chrashes completely before WM_DESTROY is reached. MS Spy reveals. 
There are some other issues too, like trying to add a patient with invalid NHS number fails without telling why and there is no error checking at file operations, etc. No need to declare procedures ahead of PBMAIN anymore and we have learned that it's safest to use MODELESS program loop for this kind of "one dialog" app's in Windows 10 and later.
I personally would not use AI for anything, because I prefer to have full control of my code from start to goal, but I can see where companies will think this is fine and so - I guess it means we can expect to se lots of buggy software in the future. Grumpy old programmer mode on...
There are some other issues too, like trying to add a patient with invalid NHS number fails without telling why and there is no error checking at file operations, etc. No need to declare procedures ahead of PBMAIN anymore and we have learned that it's safest to use MODELESS program loop for this kind of "one dialog" app's in Windows 10 and later.
I personally would not use AI for anything, because I prefer to have full control of my code from start to goal, but I can see where companies will think this is fine and so - I guess it means we can expect to se lots of buggy software in the future. Grumpy old programmer mode on...