I have run into a problem with the "compact and repair" feature on my Access
2003. Recently I had my PC upgraded and had my IT PC Technician reload
Office Professional and all upgrades, so it is current in that department.
My PC is part of a distributed network and I access and administer databases
across that same distributed network.

The problem is that when I try to compact and repair (C&R) my databases I
have some mixed results.
1) On my local drives, it works fine.
2) On the network drives/shares I have a problem that the compact and
repair works on some drives/shares and not on others.
a) It is NOT an intermittent thing, it is the same drives/shares that
don't work each time.
b) It does not appear to be related to a specific server. On at least
on server, C&R works within one share on that server and on another share it
doesn't work.

CLARIFICATION: By not working, I mean that it does the C&R...
It creates the db#.mdb, but for whatever reason(s)
it
leaves the db#.mdb orphaned and does not rename
it as the source database.

This has to be something to do with the NEW PC, because I can go to any
other PC on the network (log in with my logon) and do the C&R without issue,
regardless of the server/shares. The C&R works fine without issue(s).

My gut thinks that it has to be some kind of configuration issue... do any
of you have a recommendation where to look, or what needs to be set to
correct this issue?

Thanks in advance for your assistance. This community of users and
professionals is unparalleled, thanks again.

MJ

hi,

MJ wrote:
> I have run into a problem with the "compact and repair" feature on my Access
> 2003. Recently I had my PC upgraded and had my IT PC Technician reload
> Office Professional and all upgrades, so it is current in that department.
There have been several issues with SP3. There are hotfixes for some of
them. Ask your computer guy. Otherwise he as to unsinstall Office and
reinstall it without the SP3.


mfG
--> stefan <--

I'm betting that it's a permissions problem. You need read, write, create,
and delete (a.k.a. modify) privileges on the entire folder(s) that contains
the database files.

When they gave you the new computer, they didn't bother to give you the
needed permissions that you once had.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


"MJ" wrote:

> I have run into a problem with the "compact and repair" feature on my Access
> 2003. Recently I had my PC upgraded and had my IT PC Technician reload
> Office Professional and all upgrades, so it is current in that department.
> My PC is part of a distributed network and I access and administer databases
> across that same distributed network.
>
> The problem is that when I try to compact and repair (C&R) my databases I
> have some mixed results.
> 1) On my local drives, it works fine.
> 2) On the network drives/shares I have a problem that the compact and
> repair works on some drives/shares and not on others.
> a) It is NOT an intermittent thing, it is the same drives/shares that
> don't work each time.
> b) It does not appear to be related to a specific server. On at least
> on server, C&R works within one share on that server and on another share it
> doesn't work.
>
> CLARIFICATION: By not working, I mean that it does the C&R...
> It creates the db#.mdb, but for whatever reason(s)
> it
> leaves the db#.mdb orphaned and does not rename
> it as the source database.
>
> This has to be something to do with the NEW PC, because I can go to any
> other PC on the network (log in with my logon) and do the C&R without issue,
> regardless of the server/shares. The C&R works fine without issue(s).
>
> My gut thinks that it has to be some kind of configuration issue... do any
> of you have a recommendation where to look, or what needs to be set to
> correct this issue?
>
> Thanks in advance for your assistance. This community of users and
> professionals is unparalleled, thanks again.
>
> MJ
>

Jerry,

That's what I thought too, but as I mentioned toward the bottom of my
request for information (below) I have NO problem doing the C&R whenever
logged into another PC on the network.
1) However, I will extend that statement further to include that I have no
problem as long as the PC is NOT a SP3 machine.
* Based on an earlier reply (Stefan Hoffman), I went to several other
machines (some SP2 and others SP3) and was able to duplicate the ability to
C&R or NOT to and the common link was INDEED the difference of whether the
machine had SP3 loaded or not. While this was not a scientific test, it
definitely appears to back up the contention that this may be one of those
infamous "undocumented features" of new releases.

My only next question is, when will MS correct this issue with a fix?

Thanks again for your inputs.

Sincerely,
MJ


"Jerry Whittle" wrote:

> I'm betting that it's a permissions problem. You need read, write, create,
> and delete (a.k.a. modify) privileges on the entire folder(s) that contains
> the database files.
>
> When they gave you the new computer, they didn't bother to give you the
> needed permissions that you once had.
> --
> Jerry Whittle, Microsoft Access MVP
> Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
>
>
> "MJ" wrote:
>
> > I have run into a problem with the "compact and repair" feature on my Access
> > 2003. Recently I had my PC upgraded and had my IT PC Technician reload
> > Office Professional and all upgrades, so it is current in that department.
> > My PC is part of a distributed network and I access and administer databases
> > across that same distributed network.
> >
> > The problem is that when I try to compact and repair (C&R) my databases I
> > have some mixed results.
> > 1) On my local drives, it works fine.
> > 2) On the network drives/shares I have a problem that the compact and
> > repair works on some drives/shares and not on others.
> > a) It is NOT an intermittent thing, it is the same drives/shares that
> > don't work each time.
> > b) It does not appear to be related to a specific server. On at least
> > on server, C&R works within one share on that server and on another share it
> > doesn't work.
> >
> > CLARIFICATION: By not working, I mean that it does the C&R...
> > It creates the db#.mdb, but for whatever reason(s)
> > it
> > leaves the db#.mdb orphaned and does not rename
> > it as the source database.
> >
> > This has to be something to do with the NEW PC, because I can go to any
> > other PC on the network (log in with my logon) and do the C&R without issue,
> > regardless of the server/shares. The C&R works fine without issue(s).
> >
> > My gut thinks that it has to be some kind of configuration issue... do any
> > of you have a recommendation where to look, or what needs to be set to
> > correct this issue?
> >
> > Thanks in advance for your assistance. This community of users and
> > professionals is unparalleled, thanks again.
> >
> > MJ
> >

Stefan,

Your input got me thinking about that possibility and I was able to
dupilcate that very issue with several machines within my office. The
difference definitely appears to be whether or not the machine has SP3 loaded.

Since the servers/shares impacted by this problem do not appear to be random
and I have mapped out the ones that I cannot C&R, reblasting my machine with
a fresh load of Office and only taking it to SP2 probably is not an option
for me since there are several true enhancements that I benefit from with
SP3.

I have communicated this issue and possible connection to SP3 loads with my
IT staff. Only thing I need to remember is that if I need to C&R one of
those impacted location databases I willl need to go to a SP2 machine to
effect the C&R.

So, for others with similar problems, your options would seem to be:

1) Reset your machine to base Office load and take it up through SP2 and
current updates NOT including SP3; ... OR ...

2) Live with this "undocumented feature," simply map out which database
locations are impacted for you, and go to a non-SP3 machine to do your C&Rs.
NOTE: Just remember that you CAN do a C&R from your SP3 machine, it just
won't complete the process by renaming the newly compressed database file to
the original source database name. You could do that last step manually, if
you want to.

Thanks for your inputs. If someone else has any direct inputs that might
shine a different light on it, please let me know.

Sincerely,
MJ


"Stefan Hoffmann" wrote:

> hi,
>
> MJ wrote:
> > I have run into a problem with the "compact and repair" feature on my Access
> > 2003. Recently I had my PC upgraded and had my IT PC Technician reload
> > Office Professional and all upgrades, so it is current in that department.
> There have been several issues with SP3. There are hotfixes for some of
> them. Ask your computer guy. Otherwise he as to unsinstall Office and
> reinstall it without the SP3.
>
>
> mfG
> --> stefan <--
>

MJ <(E-Mail Removed)> wrote:

> * Based on an earlier reply (Stefan Hoffman), I went to several other
>machines (some SP2 and others SP3) and was able to duplicate the ability to
>C&R or NOT to and the common link was INDEED the difference of whether the
>machine had SP3 loaded or not. While this was not a scientific test, it
>definitely appears to back up the contention that this may be one of those
>infamous "undocumented features" of new releases.

Were you logged on to the same account when you did the C&R?

>My only next question is, when will MS correct this issue with a fix?

MS would like to know what is different about the shares in which the
C&R was successful and wasn't successful. You have stated in your
other posting that some shares worked and some didn't. MS will
require the differences so they can setup a repro situation.

You can't test to see what's fixed if you can't test in an environment
where it's broken.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/