Problem with Compact/Repair part 2

[Ron]

New discovery.

If I take a perfectly good database, and "compact/repair" on it with Access
2000 (seems to be at multiple sites--I've tried it with my system here, at
another office on an entirely different network), it damages the file
somehow. The user's machine that did the compact/repair can see the file
fine. But any networked user can't get in. I can double click on a good
database file from any user (over the network) and it loads fine (of course,
no queries/forms/reports etc cause those are all on the front end--this is
the back end). But if I run C/R on the same file, same directory,
everything...just renamed so I can revert to good data if something goes
wrong I get a message "Microsoft Access can't find the database file (double
backslash)maindrive\mainfolder\blahblah.mdb. Make sure you entered the
correct path and file name." (hello, I'm double clicking on the file out on
the networked drive...). Even have tried it after making a copy of the
database prior to C/R and, using that same file (not the copy), I run C/R
and again, that user has access. Nobody else does. Same error message.
Yet, before C/R, everything is fine..all users can open file fine.

I tried uninstalling Access, reinstalling, and no effect. Still, if I C/R
with Access 2000, it bombs when I try and open the database from any other
user. Tried using a file that I couldn't open after the C/R, doing a C/R on
another machine with Access 2003 and all users can use file. Put it back on
any Access2000 machine, do a C/R on that file, and bang...nobody but the
user who did the C/R can open the file.

File has ALWAYS been an Access2000 database.

Kicker:
Tried this same process on Northwind.mdb. Same result. After Compact/Repair,
no networked users can "find" the file...even tho they're double clicking on
it on the networked drive.

Anyone have a clue?
ron

[Larry Linson]

My guess is that some DLL or EXE used in the compact/repair process has been
corrupted on that machine. I certainly suggest not trying to compact/repair
any more DBs on the machine.

If it were mine, I wouldn't waste time trying to find the exact location of
the error, but would first uninstall and then reinstall Access, or Office
Pro. If you did not have all three Service Packs installed for Access 2000,
it was "at risk", in any case, and it is officially "out of service" under
Microsoft's service policies.

Larry Linson
Microsoft Access MVP
"Ron" <ro********************@verizon.netwrote in message
news:9pSTh.73$jR5.70@trnddc08...

New discovery.

If I take a perfectly good database, and "compact/repair" on it with
Access 2000 (seems to be at multiple sites--I've tried it with my system
here, at another office on an entirely different network), it damages the
file somehow. The user's machine that did the compact/repair can see the
file fine. But any networked user can't get in. I can double click on a
good database file from any user (over the network) and it loads fine (of
course, no queries/forms/reports etc cause those are all on the front
end--this is the back end). But if I run C/R on the same file, same
directory, everything...just renamed so I can revert to good data if
something goes wrong I get a message "Microsoft Access can't find the
database file (double backslash)maindrive\mainfolder\blahblah.mdb. Make
sure you entered the correct path and file name." (hello, I'm double
clicking on the file out on the networked drive...). Even have tried it
after making a copy of the database prior to C/R and, using that same file
(not the copy), I run C/R and again, that user has access. Nobody else
does. Same error message. Yet, before C/R, everything is fine..all users
can open file fine.

I tried uninstalling Access, reinstalling, and no effect. Still, if I C/R
with Access 2000, it bombs when I try and open the database from any other
user. Tried using a file that I couldn't open after the C/R, doing a C/R
on another machine with Access 2003 and all users can use file. Put it
back on any Access2000 machine, do a C/R on that file, and bang...nobody
but the user who did the C/R can open the file.

File has ALWAYS been an Access2000 database.

Kicker:
Tried this same process on Northwind.mdb. Same result. After
Compact/Repair, no networked users can "find" the file...even tho they're
double clicking on it on the networked drive.

Anyone have a clue?
ron

[John Mishefske]

Ron wrote:

New discovery.

If I take a perfectly good database, and "compact/repair" on it with Access
2000 (seems to be at multiple sites--I've tried it with my system here, at
another office on an entirely different network), it damages the file
somehow. The user's machine that did the compact/repair can see the file
fine. But any networked user can't get in. I can double click on a good
database file from any user (over the network) and it loads fine (of course,
no queries/forms/reports etc cause those are all on the front end--this is
the back end). But if I run C/R on the same file, same directory,
everything...just renamed so I can revert to good data if something goes
wrong I get a message "Microsoft Access can't find the database file (double
backslash)maindrive\mainfolder\blahblah.mdb. Make sure you entered the
correct path and file name." (hello, I'm double clicking on the file out on
the networked drive...). Even have tried it after making a copy of the
database prior to C/R and, using that same file (not the copy), I run C/R
and again, that user has access. Nobody else does. Same error message.
Yet, before C/R, everything is fine..all users can open file fine.

I tried uninstalling Access, reinstalling, and no effect. Still, if I C/R
with Access 2000, it bombs when I try and open the database from any other
user. Tried using a file that I couldn't open after the C/R, doing a C/R on
another machine with Access 2003 and all users can use file. Put it back on
any Access2000 machine, do a C/R on that file, and bang...nobody but the
user who did the C/R can open the file.

File has ALWAYS been an Access2000 database.

Kicker:
Tried this same process on Northwind.mdb. Same result. After Compact/Repair,
no networked users can "find" the file...even tho they're double clicking on
it on the networked drive.

Anyone have a clue?

A2000 creates a temp database outside the CurrentProject.Path folder and
then copies it back to that folder when it does a compact. Unfortunately
it then inherits the permission of that user's TEMP folder which is
the last user to use the app.

Try opening up the permissions on your defined TEMP directory - that worked
for me. See:

http://support.microsoft.com/default...b;en-us;295234
--
---------------
John Mishefske, Microsoft Access MVP

[Ron]

As I indicated, I have uninstalled, reinstalled Access. Now I'll have to
get the same service packs that I did have prior to this.

And, again as indicated, I also have tried other computers with like Access
versions of Access. All do the same thing.

However, that did make me think... maybe it's something new in an automatic
update for WinXP or something. Something other than Access.

Something must have changed along the way, somewhere. All these computers
I'm using to try different solutions/fixes that I've thought up have been
fine in the past with compact/repairing... so it must be something new
that's been introduced in the last couple months to these machines.
Introduced somehow.

Since I can't give up (I'd have to find another money stream), I'll keep
trying different things.

Thanks for your response.
ron

"Larry Linson" <bo*****@localhost.notwrote in message
news:90VTh.568$h8.194@trnddc06...

My guess is that some DLL or EXE used in the compact/repair process has
been corrupted on that machine. I certainly suggest not trying to
compact/repair any more DBs on the machine.

If it were mine, I wouldn't waste time trying to find the exact location
of the error, but would first uninstall and then reinstall Access, or
Office Pro. If you did not have all three Service Packs installed for
Access 2000, it was "at risk", in any case, and it is officially "out of
service" under Microsoft's service policies.

Larry Linson
Microsoft Access MVP
"Ron" <ro********************@verizon.netwrote in message
news:9pSTh.73$jR5.70@trnddc08...

>New discovery.

If I take a perfectly good database, and "compact/repair" on it with
Access 2000 (seems to be at multiple sites--I've tried it with my system
here, at another office on an entirely different network), it damages the
file somehow. The user's machine that did the compact/repair can see the
file fine. But any networked user can't get in. I can double click on a
good database file from any user (over the network) and it loads fine (of
course, no queries/forms/reports etc cause those are all on the front
end--this is the back end). But if I run C/R on the same file, same
directory, everything...just renamed so I can revert to good data if
something goes wrong I get a message "Microsoft Access can't find the
database file (double backslash)maindrive\mainfolder\blahblah.mdb. Make
sure you entered the correct path and file name." (hello, I'm double
clicking on the file out on the networked drive...). Even have tried it
after making a copy of the database prior to C/R and, using that same
file (not the copy), I run C/R and again, that user has access. Nobody
else does. Same error message. Yet, before C/R, everything is fine..all
users can open file fine.

I tried uninstalling Access, reinstalling, and no effect. Still, if I
C/R with Access 2000, it bombs when I try and open the database from any
other user. Tried using a file that I couldn't open after the C/R, doing
a C/R on another machine with Access 2003 and all users can use file.
Put it back on any Access2000 machine, do a C/R on that file, and
bang...nobody but the user who did the C/R can open the file.

File has ALWAYS been an Access2000 database.

Kicker:
Tried this same process on Northwind.mdb. Same result. After
Compact/Repair, no networked users can "find" the file...even tho they're
double clicking on it on the networked drive.

Anyone have a clue?
ron

[John Mishefske]

Ron wrote:

As I indicated, I have uninstalled, reinstalled Access. Now I'll have to
get the same service packs that I did have prior to this.

And, again as indicated, I also have tried other computers with like Access
versions of Access. All do the same thing.

However, that did make me think... maybe it's something new in an automatic
update for WinXP or something. Something other than Access.

Something must have changed along the way, somewhere. All these computers
I'm using to try different solutions/fixes that I've thought up have been
fine in the past with compact/repairing... so it must be something new
that's been introduced in the last couple months to these machines.
Introduced somehow.

Since I can't give up (I'd have to find another money stream), I'll keep
trying different things.

Ron - did you see my previous post? You should check this out and see if you can eliminate
it as the source of your problem.

-------------------

A2000 creates a temp database outside the CurrentProject.Path folder and
then copies it back to that folder when it does a compact. Unfortunately
it then inherits the permission of that user's TEMP folder which is
the last user to use the app.

Try opening up the permissions on your defined TEMP directory - that worked
for me. See:

http://support.microsoft.com/default...b;en-us;295234

--
---------------
John Mishefske, Microsoft Access MVP

[Albert D. Kallal]

Remember, if someone gives you a file on a floppy disk, and you then insert
the floppy disk, and drag the file to your desktop.

Now, drag that file to a network folder..and guess what? No one on the
network can use the file? this can be a text file, a excel file..even a word
file...

Why?

Because windows xp allows you to assign file permissions to a INDIVIDUAL
FILE!!!

When you place the file on your desktop, it inherits your file permissions
that are assigned to your workstation...
When you then copy the file to the network drive..it continues to have the
file permissions that YOUR computer assigned to the file....

A compact and repair actually makes a copy of the file..and thus this opens
up a point in time in which file permissions can be changed......

This is not really a ms-access issue as much a simple file copy when using
windows xp can dramatically change the file permissions assigned to a
file....

See John's post for furhter notes of this issue...
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com

[Ron]

YES!

This did the trick.

Now, can anyone explain why this all of a sudden has started happening?
I've been working on the same computer, same files, same network, etc for
over a year...and NEVER had this happen before.

But sure enough, now, every file I compact/repair I then have to go in and
change the security settings for. And, EVERY time I compact/repair any of
the mdb's I have to reset this security area.

When/how did this all change? I didn't knowingly change any security
setting to have this start happening.

Is there a way to reset a "user" I'm on when compacting/repairing so the
"temp" file used will allow others to use the file? Otherwise, I'll never
be able to allow my users to compact/repair their own database (without also
teaching them this malarkey) which isn't the most efficient way to go, IMHO.

This probably needs to be brought up on another newsgroup?

Thanks John and Larry for staying with me and helping on this issue--I
really appreciate your time and knowledge!

ron

"John Mishefske" <jm**********@SPAMyahoo.comwrote in message
news:46***********************@roadrunner.com...

Ron wrote:

>New discovery.

If I take a perfectly good database, and "compact/repair" on it with
Access 2000 (seems to be at multiple sites--I've tried it with my system
here, at another office on an entirely different network), it damages the
file somehow. The user's machine that did the compact/repair can see the
file fine. But any networked user can't get in. I can double click on a
good database file from any user (over the network) and it loads fine (of
course, no queries/forms/reports etc cause those are all on the front
end--this is the back end). But if I run C/R on the same file, same
directory, everything...just renamed so I can revert to good data if
something goes wrong I get a message "Microsoft Access can't find the
database file (double backslash)maindrive\mainfolder\blahblah.mdb. Make
sure you entered the correct path and file name." (hello, I'm double
clicking on the file out on the networked drive...). Even have tried it
after making a copy of the database prior to C/R and, using that same
file (not the copy), I run C/R and again, that user has access. Nobody
else does. Same error message. Yet, before C/R, everything is fine..all
users can open file fine.

I tried uninstalling Access, reinstalling, and no effect. Still, if I
C/R with Access 2000, it bombs when I try and open the database from any
other user. Tried using a file that I couldn't open after the C/R, doing
a C/R on another machine with Access 2003 and all users can use file.
Put it back on any Access2000 machine, do a C/R on that file, and
bang...nobody but the user who did the C/R can open the file.

File has ALWAYS been an Access2000 database.

Kicker:
Tried this same process on Northwind.mdb. Same result. After
Compact/Repair, no networked users can "find" the file...even tho they're
double clicking on it on the networked drive.

Anyone have a clue?

A2000 creates a temp database outside the CurrentProject.Path folder and
then copies it back to that folder when it does a compact. Unfortunately
it then inherits the permission of that user's TEMP folder which is
the last user to use the app.

Try opening up the permissions on your defined TEMP directory - that
worked
for me. See:

http://support.microsoft.com/default...b;en-us;295234
--
---------------
John Mishefske, Microsoft Access MVP

[Ron]

Yeah, this turned out to be the problem I am encountering. I just don't
understand what changed--I've compact/repaired this file many times
previously, not only on this computer, but other files on other computers,
and never had this problem before. So, what changed?

And how do I get my old world back so this isn't a problem every time I
compact/repair? On any computer I'm on, I'm using the administrator account,
so I don't see why the security is limiting like this. Perhaps I'll zip
into the WinXP security NG's for some browsing.

Thanks for your response,
ron

"Albert D. Kallal" <Pl*******************@msn.comwrote in message
news:Lp4Uh.71513$DE1.58627@pd7urf2no...

Remember, if someone gives you a file on a floppy disk, and you then
insert the floppy disk, and drag the file to your desktop.

Now, drag that file to a network folder..and guess what? No one on the
network can use the file? this can be a text file, a excel file..even a
word file...

Why?

Because windows xp allows you to assign file permissions to a INDIVIDUAL
FILE!!!

When you place the file on your desktop, it inherits your file permissions
that are assigned to your workstation...
When you then copy the file to the network drive..it continues to have the
file permissions that YOUR computer assigned to the file....

A compact and repair actually makes a copy of the file..and thus this
opens up a point in time in which file permissions can be changed......

This is not really a ms-access issue as much a simple file copy when using
windows xp can dramatically change the file permissions assigned to a
file....

See John's post for furhter notes of this issue...
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com

[John Mishefske]

Ron wrote:

Yeah, this turned out to be the problem I am encountering. I just don't
understand what changed--I've compact/repaired this file many times
previously, not only on this computer, but other files on other computers,
and never had this problem before. So, what changed?

And how do I get my old world back so this isn't a problem every time I
compact/repair? On any computer I'm on, I'm using the administrator account,
so I don't see why the security is limiting like this. Perhaps I'll zip
into the WinXP security NG's for some browsing.

Did you start using Compact On Close option? Or change your compact routine?

Is it possible that the defined %TEMP% value was changed in your environment or on a
specific PC?

Or maybe someone changed permissions for users/groups? Or you just implemented NTFS? (Now
I'm reaching...)

I seem to recall this issue didn't bite me until we moved to XP but can't recall if that
is actually true.

As Albert pointed out this isn't really an issue with Access although different versions
use different locations for the compact/repair and that does cause some issues when moving
to a new version. I think the KB I referenced points out the different locations used in
each version.

I've posted this issue to the newsgroup many times over the years...

--
---------------
John Mishefske, Microsoft Access MVP

[Ron]

Hi John,

See my responses below...

"John Mishefske" <jm**********@SPAMyahoo.comwrote in message
news:46**********************@roadrunner.com...

Ron wrote:

>Yeah, this turned out to be the problem I am encountering. I just don't
understand what changed--I've compact/repaired this file many times
previously, not only on this computer, but other files on other
computers, and never had this problem before. So, what changed?

And how do I get my old world back so this isn't a problem every time I
compact/repair? On any computer I'm on, I'm using the administrator
account, so I don't see why the security is limiting like this. Perhaps
I'll zip into the WinXP security NG's for some browsing.

Did you start using Compact On Close option? Or change your compact
routine?

No, no Compact On Close--I've read that's not a wise idea so have never done
it. No changes to compact routine. My data files at my office are not
normally multi-used. I'll set up a new datafile for a company, put it on
their system AFTER compacting/repairing (lots of temp files to transfer old
program data to this new one, temp data files, queries, etc so NEED a
compact/repair after transfers and before delivery. All delivered databases
have worked fine under multiuser situations when they've been delivered.
However, tried to compact/repair a database on a client's system (that's
been working fine for 6 months) and ran into this problem. Brought the data
back here, and had the same problem. Looked at some other files, and ones
that were fine before, once compacted/repaired NOW I can't get into with
anyone but original user's system. That's when I kinda knew something had
changed between last client supplied data and now. It HAS to be an
automatic update to something...I haven't manually updated anything, nor
changed security settings (knowingly anyway).

Is it possible that the defined %TEMP% value was changed in your
environment or on a specific PC?

Wouldn't know how to change a %TEMP% value if one came up and bit me. I'd
like to know though, so I can change it back to what it was and avoid all
this malarkey. Right now, it seems I'll always have to copy the clien'ts
file to my system, compact/repair, then put "Everyone" back to "full
access", then send the file back. I'll apparently have to do that because
when I tried to do it on this one client's system when I right click on the
datafile at their site, I don't get a "Security" tab on the properties.
Only on mine (so far--haven't looked at any other client's systems yet).
I'm not exactly a "security" kinda dude--I let others install networks,
establish security, etc. Once it's all set up and working, I come in with
the program/datafiles needed to do their jobs. At least that's the way I've
handled it in the past--but this situation may require me to alter this way
of doing busines.

Or maybe someone changed permissions for users/groups? Or you just
implemented NTFS? (Now I'm reaching...)

Not that I'm aware (for client), and certainly not for my system. It's
gotta be some kinda automatic update that changed the "assumptions" security
requires. Do you know anything about changing them back? I know that's
kinda off-topic, but it still has to do with Access, eh?

Been using same system (with NTFS--WinXP Pro) for 2 years. No changes that
I'm aware of.

I seem to recall this issue didn't bite me until we moved to XP but can't
recall if that is actually true.

As Albert pointed out this isn't really an issue with Access although
different versions use different locations for the compact/repair and that
does cause some issues when moving to a new version. I think the KB I
referenced points out the different locations used in each version.

I've posted this issue to the newsgroup many times over the years...

Well, like I wrote before...thank you very much for answering my post. I
was ready to pull my hair out--and I can't really afford to lose any...
::grin::

ron

--
---------------
John Mishefske, Microsoft Access MVP