FiveTech Software tech support forums

... extension, but the files listed in the incremental search include ".mdb" files as well, it does not however include "*.ldb" of which these type files exists. Is there a way to specify what extension in the incremental search options? Thanks, Byron ...

Enrico and Rao I tested the oRs:CLose() followed up with oRs := nil and releasing the object did not close the .ldb for me .. however if I inserted oRs:ActiveConnection:Close() .. the .ldb went away. I need to update this post and let you both know that oRs := nil DOES release ...

Rick, I need to update this post and let you both know that oRs := nil DOES release the object as well as the connection .. the .ldb does in fact close when you nil out the recordset object! I went back and looked at my example .. and I had an additional call to a verification table after ...

Enrico and Rao I tested the oRs:CLose() followed up with oRs := nil and releasing the object did not close the .ldb for me .. however if I inserted oRs:ActiveConnection:Close() .. the .ldb went away. I need to update this post and let you both know that oRs := nil DOES release ...

Enrico and Rao I tested the oRs:CLose() followed up with oRs := nil and releasing the object did not close the .ldb for me .. however if I inserted oRs:ActiveConnection:Close() .. the .ldb went away. My example was just a simple case of opening a table .. reading data and writing ...

... the example is not correct. Once oRs either goes out of scope or set to nil, the active connection is closed. Please look carefully at my sample. LDB file is still there even after the second message, when oRs has already gone out of scope. EMG

Let us continue the discussion in the other thread

NageswaraRao, Please check the sample below (change table and field name). You will see that LDB is automatically deleted only if you remove the BUTTON. #include "Fivewin.ch"#define adOpenForwardOnly 0#define adOpenKeyset      1#define adOpenDynamic     2#define ...

NageswaraRao, So, after browsing please do this: =============== After browsing in a dialog: ACTIVATE DIALOG oBrw:oRs := nil oRs:Close() oRs := nil If you are browing in an MDICHILD: oWnd:bPostEnd := { || oBrw:oRs := nil, oRs:Close(), oRs := nil } ================ Now surely the ActiveConnection of ...

Mr Rick Using a single connection and closing the connection while exiting the application surely works well. But let us continue testing your former approach. After opening RecordSet you normally use it for browing. After you exit browse you write ----- oRs:Close() oRs := nil ------ Still oBrw:oRs ...

NageswaraRao,

nageswaragunupudi wrote:So, for now, it may be safer to close oRs:ActiveConnection also.

I'm not so sure. If there is an active reference to oRs somewhere then closing the connection can cause errors elsewhere.

EMG

Mr EMG Suppose so. It IS so. I am testing. After some preliminary tests, I can now confirm that in fact it is so. I get back to you with more details later, but broadly what is happening is this. After we open a recordset, we are not just doing simple operations and closing the recordset. We use the...

NageswaraRao,

nageswaragunupudi wrote:I got your point. I am working on this.
It also means "all references in the memory" to this recordset object should go out of scope. Right?

Suppose so.

EMG

Rick, Is it the same problem that I had in this topic? I couldn't delete the file brcause it was not completely closed. http://forums.fivetechsupport.com/viewtopic.php?f=3&t=26787 Mr Mark Unless we test with simplest possible code, we can not figure out whats going wrong and why...

... Sql statement and a connection string, OR a pre-opened global connection OBJECT. What I did not know is that when working with Ms Access .. the .ldb does not necessarily go away when you Close() a recordset specifically created with a connection string. So as you open and close many recordsets, ...