Open tables after ending app. 1

[florindaniel]

Hello,
Monitoring the network connection of a workstation, I've noticed this peculiar behaviour:
some files (tables, cdx-es) appear as open in the server manage screen after the form or even
App that used them is closed (that's even if I Refresh the server manager).
The file handlers look like being in use for some seconds (10 even); I've tried to FLUSH FORCE
after closing tables but there was no difference.
Is it because of the Windows Server, could it be harmful (like losing data), or it's only
about displaying some information?

Thank you
Daniel

 

[GriffMG]

Perhaps it's an opp' locking feature - takes a while to let go of the files.

Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

 

[Mike Lewis]

I'm not sure why this is happening, Daniel. But it's unlikely to be harmful. All your data should be safely written by the time you close the tables or exit the app. Even if the committing of the data was delayed (and I don't think it is), it would only be a problem if the server crashed in the few seconds in question.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads

 

[Dan Freeman]

Is the application exiting for sure?

I've seen cases where the developer didn't issue a CLEAR READ to release the READ EVENTS so the application appeared to exit properly and was no longer visible on the PC but was still in the Windows task list (and holding files open).

 

[JRB-Bldr]

One tool that I use to confirm if someone has a table 'engaged' whether intentionally or a network 'holdover' is WhoHasNT (

http://www.gadgetfactory.com/whohasnt.shtml

)

With it I can not only see who the system 'thinks' has the table engaged, but I can Clear the 'engagement'.

I too have found a few times when the network 'thinks' a data table is still 'engaged' by a user, when they are not in the application. Not very often, but sometimes and I have no idea why/under what circumstances this occurs.

When that happens a ReStart/ReBoot of their workstation seems to clear it up, but in the absence of that, using that tool has cleared things up.

it's unlikely to be harmful.
Maybe true, but if data table maintenance needs to be performed (especially if it is periodically automated) and that maintenance utility cannot get the table(s) EXCLUSIVELY, then No Maintenance.

Good Luck,
JRB-Bldr