Table Resturcturing Error - table being used

[jeffemery]

We have been an Alpha user since 1995 with hundreds of tables and sets. Within the last 3 weeks we began encountering a odd error. When restructuring a table, ie - adding a new field or changing a field length, we get the following error AFTER we have made the table change and have selected Save. "The process cannot access the file because it is being used by another process."

We know for certain that no other activity is using the table in question, or the entire Alpha system, for that matter. We have tried copying out the database to other systems and get the same error. We do not get this all of the time, but we have noticed it is occurring more frequently. We have also noticed that even though we get the 'being used' error when trying to restructure a table, we can still rebuild it's indexes or Pack the table ... activities which we should not be able to do if the table was truly 'being used'.

We have been playing with this for days, without a clue as to why we are seeing the 'being used' message. Does anyone have any thoughts?

[CraigSchumacker]

I am not, nor have I ever had an issue like the one you describe. I'm thinking the issue is yours, alone.

Have you changed the version of AA you were using anytime recently? If not, that takes AA out of the scope of the cause.

You may have scripts opening tables, and the pointer is not being closed at script completion.

There may be errors in scripts where the script does not complete, so the table is not closed.

The server where the data is being stored may be scanning with an AV software, or backing up, or other activity that flags the file set associated with the table as in use.

The next time it happens, go to the file server and see who or what has the file open. If Windows, then go to Control Panel - Administrative Tools - Computer Management - Shared Folders - Open Files.

A bit of detective work from there might help you close in on the issue.

Just for the sake of the try, have you done a backup and then a database compact?

Is it possible a user is closing the AA app on his computer, and it's hanging - visible only in task manager?

Or are you using A5.HIDE()?

I know these are long shots, but it's where I'd start.

[Al Buchholz]

What backup system are you using for those machines?

Is it possible that the interference is coming from that?

[jeffemery]

We use a Datto Backup and Recovery Appliance. It has been running for several months now without incidence. Still, an interesting thought, Al. We also began using Alpha Release 6699 just prior to these table restructure issues. Coincidence? Probably .....

We are now testing this problem with prior Releases of Alpha on isolated copies of our Data Base; machines with nothing else running on them.

Thank you Al and Craig for your thoughts ...

[Al Buchholz]

We use a Datto Backup and Recovery Appliance. It has been running for several months now without incidence. Still, an interesting thought, Al. We also began using Alpha Release 6699 just prior to these table restructure issues. Coincidence? Probably .....

We are now testing this problem with prior Releases of Alpha on isolated copies of our Data Base; machines with nothing else running on them.

Thank you Al and Craig for your thoughts ...

Did you try to restructure prior to upgrading Alpha?

So you have 2 tests to run.

1. is to roll back to the previous version of Alpha.
If you have a test machine that is where to do that.

2. stop the backup system or do it on a test system that isn't being backed up on a directory that isn't part of the backup. (probably better)

You want to do those steps separately so you know what part is the issue.

I'd a third test also.

Duplicate (data, field rules, all options - ie a complete duplication) the table to a new name - shorter than 10 characters and try to restructure that table

Duplicating is a magic pill that solves a lot of internal problems.

[roy]

I've had this same issue pop up. Did you find the cause?

Thanks

[jeffemery]

Hi Roy -

We've have been taken away from this issue for a few weeks, but need to get back on it. The problem remains the same, and we have found no cause as of yet. It has not, as of now, caused us any operational issues, but it makes me nervous. I have contacted Alpha for help, but found none that was any value. I am now working with an outside consultant who has been far more helpful.

Interesting point. While we cannot add a field to a table using the interface on the Control Panel --> filename-->Edit Structure, we can add a field using the TABLE.ADD_FIELDS() function in an xbasic script. Go figure. Why one works and not the other I am hoping will be a clue to someone more knowledgeable than I am.

I'll post any progress I make here.

Jeff

[jeffemery]

Roy -

One more note. Occasionally, after doing a Workspace Compact, we will be able to add a field or two, then Alpha reverts back to the same problems. I have a sense that the issue is somehow related to the Application Workspace, but I am not knowledgeable enough to know what that might be.

Jeff

[roy]

Thanks for your reply Jeff.

My problem is that a set will not load due to the "used by another process" error of a certain child table, but other sets with the same child table link do not have the problem. I've found that doing a workspace compact does resolve the issue, for a time, then it happens again. I'll report back if I find any other resolution.

Roy

[Ted Giles]

It sounds a lot like a Naming Issue. As Al pointed out, the 10 char length of field names is important.
I only use 8 char and never names where the the leading characters are too similar.
There have been quite a few jobs where the developer - years back - named fields as;

Customersname
Customersaddress1
Customersaddress2
Etc.
This is an anathema to Alpha and confuses links and indices.

Follow Al's suggestions as recent changes to Windows security can cloud the issue.
When a Windows update is running in the background you can seem to get spurious problems, so suggest you check what's going on when errors occur.

[martinwcole]

Tables and related files can get locked open - outside Alpha completely.
If you can, restart the server, which may fix the issue.
Also, call your IT man and ask him to close all instances of the table and related files.

[jeffemery]

We first reported this problem in July of 2020; it has yet to be resolved. Things have deteriorated somewhat since then. Using Alpha's 'Menu System', we can not add fields to tables, tables to a set, or complete a Workspace Compact. We can do these things using Xbasic Functions and that works pretty well most of time.

We have isolated our application to a machine with no other purpose; same problem. We have used new and old releases of Alpha with no effect. We are now back looking at this problem again to see if we might isolate an issue within our data base.

[Ted Giles]

I have encountered issues recently.
It depends where the application is saved.
Recent Windows restrictions make using the C drive a potential problem.
If you have the option, place the Alpha app outside of the C drive, and definitely NOT in the Prog Files directory.
The issue seems to be in the access rules for the C drive - dictated by Msoft - I suggest.
Alpha may not be an acceptable or authenticated application engine as far as Msoft is concerned.
If it's not Alpha, cos you have tried different versions, look at the Msoft side and run Alpha in Administrator mode.
Just saying.