One more time...
This version includes one new command. BD_SetDebugMode().
This allows the programmer to be able to debug his ADO commands a bit easier so they don't spend two days thinking there's a bug in the DLL when there's really not.......... Ahem. If the debug mode is set to on, then any DLL commands that result in an error will bring up a windows messagebox stating that error.
This is basically a stopgap solution until I add BD_GetLastErrorNumber() and BD_GetLastErrorDescription() which will all the programmer to programmatically handle DLL errors.
In the meantime, hope this helps a bit.
<<link removed -- see RC6 thread >>
Kanati
This version includes one new command. BD_SetDebugMode().
This allows the programmer to be able to debug his ADO commands a bit easier so they don't spend two days thinking there's a bug in the DLL when there's really not.......... Ahem. If the debug mode is set to on, then any DLL commands that result in an error will bring up a windows messagebox stating that error.
This is basically a stopgap solution until I add BD_GetLastErrorNumber() and BD_GetLastErrorDescription() which will all the programmer to programmatically handle DLL errors.
In the meantime, hope this helps a bit.
<<link removed -- see RC6 thread >>
Kanati