tables not closing

[davidv43]

IS anyone else having problems with tables not closing after running an operation? I am appending records to an existing file. However, when I try to change anything else with that table, such as field rules, I get an error message saying that the table is still open.

Might this be a windows 7 quirk?

[martinwcole]

Re: tables not closing

The error has been around for several years, but is often inconsistemt. Will in one case and won't in another.

the work-a-round is to put the operation in a script

however

if you can make a dummy database, and can have an operation to run, and after that easily show the error - report it as a bug and include the database - maybe they will look into it

[csda1]

Re: tables not closing

Hi David,

IS anyone else having problems with tables not closing after running an operation? I am appending records to an existing file. However, when I try to change anything else with that table, such as field rules, I get an error message saying that the table is still open.

If the append is running asynchronously, (in a different session/thread), and most likely is, it could very well have the table until completely done. The question is, do you wait for it to be done?

Might this be a windows 7 quirk?

Probably not.

the work-a-round is to put the operation in a script

Other than delaying the process a small bit, this will have no effect at all! An operation is just a bunch of XBasic code, running identically to the underlying code.

As I've said countless times before, and some people haven't been listening, is put the code

IN A FUNCTION

and the results should be much better. See my Function vs Scripts tips here

[martinwcole]

Re: tables not closing

yes - meant to say put the code in a function

Ira, you have heard of this, haven't you? That running from code vs an operation removes the periodic 'leaving the table open' issue.

[Steve Workings]

Re: tables not closing

I have a similar situation, but different cause, and I can't track it down. This is in version 9, but the thread is pertinent.

Workstation A prints a report, based on MyTable.dbf.

Other workstations that subsequently need MyTable.dbf in exclusive mode
are locked out. In fact, you can do this on Workstation B:

?table.in_use("MyTable.dbf")
= .T.

In other words, it appears as if the very act of printing a report is
leaving a table open, even when printing is way done.

Anyone ever deal with and resolve this?

[csda1]

Re: tables not closing

Hi Steve,

In other words, it appears as if the very act of printing a report is leaving a table open, even when printing is way done.

Anyone ever deal with and resolve this?

Wrap the printing report code in a function. In most cases, the finishing of the function closes the table. However, just to be sure, close the table if it is open.

One sledgehammer way to close open tables in orphaned sessions is to place this code at the end of the code/function

a5_ForceCloseTables()

Another way and possibly also required is to do

IF table.in_use("MyTable.dbf")
tbl=table.open(tablename,FILE_REUSE_EXISTING)
tbl.close()
END IF

[martinwcole]

Re: tables not closing

Steve, I don't know if your situation would lend itself to trying in V8 and V10, but I run into an issue-a-day with V9 that doesn't occur in V8 or V10.

I hope that particular issue doesn't occur in V10.

[Steve Workings]

Re: tables not closing

Yup, this is a V9 issue that has the customer running back to V8 for a lot of things, and stopped full implementation of V9. I dunno if V10 has it or not, but this customer probably won't upgrade to V10 unless V9 finally works.