Weird problem with make table query!

  • Thread starter Thread starter Ragnar Midtskogen
  • Start date Start date
R

Ragnar Midtskogen

Hello,

One of our clients has an Access 97 application running on network of Win
NT machines. A couple of days ago.the application suddenly started acting
up.

The application has a macro (this is an old application, originally created
in Access 2), that runs a make table query creating a table in aniother
Access application. This has worked fine for 10 years or so, now when the
query runs the current table is deleted, as it should be, but then there is
a message that Access stopped running the query because another user was
trying to update the same data.
The rest of the application works fine.

I have tried rebuilding both applications by copying the objects into a
blank DB file, but the problem is still there.
Many users share the same files on a server, and all have the same problem.
I tried putting the rebuilt files on one of the workstation, still the same
problem.

I brought both files back and they run fine on my computer, so the problem
must have something to do with the environment at the client's, but I can't
figure what the problem could be. They have a guy who set up and maintains
their computers and network, and he is stumped too. He thought it was an
Access problem, that is why he called me.

A few times I have run into a problem that may have the same cause. The
application creates a temporary text file, deleting the old one, and
sometimes a user would get a message that the file could not be deleted
because it was opened by another user. If the last user who created the file
closed Access then it would be OK. It looked like NT did not mark the file
as freed.

The application closed the file properly and destroyed the file handle. To
be completely safe I rewrote the application to delete the file after use.

I posted here, since the problem shows up with this query, I think I will
try the Windows NT and maybe networking.

Any help would be appreciated.

Ragnar
 
I was able to solve the problem by using Jetcomp to compact the two files,
plus the back-end DB for the application with the macro. My guess is that
the source data to be copied into the new table was corrupt.

Ragnar
 
Back
Top