File SYSTEM.MDW

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have noticed 3 occurences of a system file named SYSTEM.MDW in the
following 3 locations on my system (Win 2000 and Access 2003).

C:\Documents and Settings\My Profile Name\Application Data\Microsoft\Access

C:\Program Files\Fichiers communs\System

C:\Program Files\Microsoft Office\Office

All 3 files have data in the hidden tables (I have not modified any data)

My question: Are all 3 SYSTEM.MDW required or should I delete 2, keeping
only one for the system usage ?

I'm experiencing some intermittent problem related to mdb ownership (I can't
modify
a form and I'm getting a message saying another user is using the form,
while I'm in
a single user environment) and I suspect the problem might be related to
Acces itself
more than to my application.

FYI, few weeks ago, I have tried to find a way to have a control in my front
end mdb to
initiate a compact of the back end mdb, with no succes. In this process, I
have added one instruction
in many instances in my code in my front end mdb to close the back end mdb
(BachEndMdbName.close).
I think my problems started then, but not 100% sure.

Any help would be appreciated.
 
Michel Boivin said:
I have noticed 3 occurences of a system file named SYSTEM.MDW in the
following 3 locations on my system (Win 2000 and Access 2003).

C:\Documents and Settings\My Profile Name\Application Data\Microsoft\Access

C:\Program Files\Fichiers communs\System

C:\Program Files\Microsoft Office\Office

All 3 files have data in the hidden tables (I have not modified any data)

My question: Are all 3 SYSTEM.MDW required or should I delete 2, keeping
only one for the system usage ?
Click to expand...

I would leave them alone as "something" might be making use of each of them. If
you open Access you can look in the Workgroup Administration Utility to see
which is your default workgroup file. That is the only one you need to be
concerned with.
 
Thank you very much Rick.

This info is new to me and it will help me to continue debugging.

"Rick Brandt" a écrit :
 
Michel said:
I have noticed 3 occurences of a system file named SYSTEM.MDW in the
following 3 locations on my system (Win 2000 and Access 2003).

C:\Documents and Settings\My Profile Name\Application
Data\Microsoft\Access

C:\Program Files\Fichiers communs\System

C:\Program Files\Microsoft Office\Office

All 3 files have data in the hidden tables (I have not modified any
data)

My question: Are all 3 SYSTEM.MDW required or should I delete 2,
keeping only one for the system usage ?

I'm experiencing some intermittent problem related to mdb ownership
(I can't modify
a form and I'm getting a message saying another user is using the
form, while I'm in
a single user environment) and I suspect the problem might be related
to Acces itself
more than to my application.

FYI, few weeks ago, I have tried to find a way to have a control in
my front end mdb to
initiate a compact of the back end mdb, with no succes. In this
process, I have added one instruction
in many instances in my code in my front end mdb to close the back
end mdb (BachEndMdbName.close).
I think my problems started then, but not 100% sure.

Any help would be appreciated.
Click to expand...

Since they could all be in use by different databases, I suggest leaving
them. They should not be interfering with each other.
 
Michel Boivin said:
I have noticed 3 occurences of a system file named SYSTEM.MDW in the
following 3 locations on my system (Win 2000 and Access 2003).

C:\Documents and Settings\My Profile Name\Application
Data\Microsoft\Access

C:\Program Files\Fichiers communs\System

C:\Program Files\Microsoft Office\Office

All 3 files have data in the hidden tables (I have not modified any
data)

My question: Are all 3 SYSTEM.MDW required or should I delete 2,
keeping only one for the system usage ?

I'm experiencing some intermittent problem related to mdb ownership
(I can't modify
a form and I'm getting a message saying another user is using the
form, while I'm in
a single user environment) and I suspect the problem might be related
to Acces itself
more than to my application.

FYI, few weeks ago, I have tried to find a way to have a control in
my front end mdb to
initiate a compact of the back end mdb, with no succes. In this
process, I have added one instruction
in many instances in my code in my front end mdb to close the back
end mdb (BachEndMdbName.close).
I think my problems started then, but not 100% sure.

Any help would be appreciated.
Click to expand...

As others have said, these MDW files aren't the source of your problem.
You *may* have a problem with .LDB (record-locking) files being created
and not destroyed. Since you have a front-end and a back-end database,
be aware that an .LDB file will be created both for the front-end (in
the front-end folder) and for the back-end (in the back-end folder).
Access needs to be able to delete these files when the last user is out
of each database, so that means you must have full permissions,
including delete permissions, in both of those folders. If you are sure
that there is no one in the database (front-end or back-end), check in
those folders for an .LDB file with the same name as the .MDB file, and
delete it.

I suspect that your code to compact the back-end database may be
incorrect, though whether that is the cause of the problem you're having
now is hard to say. Would you like to post that code?
 
Back
Top