Belated thanks... that works well. Do you maintain any sort of mechanism for closing open connections when adapters are destroyed, in order to keep them from accumulating? I tried to do that by modifing my adapter class to store the handle assigned returned form my connection manager in a custom property (odbchandle), and then calling SQLDISCONNECT(This.odbchandle) in its AfterCursorClose event. A look at the open connections in my back end database (Firebird) confirms this does release the connection when the containing form is released. However, but the next time I try to run that form, or any other other containing that same adapter, I receive a 1466 ("invalid connection handle)" error in the adapter's AfterCursorFill. It seems that that =gethandle() isn't honored when the form and its adapter are instantiated a second time. DISPLAY OBJECTS verifies that both were released the first time. Maybe something is getting cached somewhere....
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only