Ron Carr said:
I installed a 2007 runtime, but found that an .mdb file is no longer
available on my client's workstations: rather there is an .accdr file.
How would I insert a new .mdb? (Data file is a backend). (i.e.,
maintenance
problem - what if I make changes)
The above seems a little bit strange to have occurred all by itself? Where
did the mdb file go? It can't just disappear into thin air all by itself?
You are asking how to insert a new mdb, but then you telling me that the
actually don't have mdb's files anymore? that doesn't make a whole lot of
sense, does it???
If you can't create accDE (or accDR's), then try running the mde with the
2007 runtime....it should work...
So I tried a 2003 runtime, which does install a .mdb that I could easily
replace. This is coming up with all of the Macro security warnings at
startup, which I can't turn off.
Why try the 2003 runtime "before" you tried running your mde? You should at
least have try running the mde on that computer, it likely would have worked
OK.
Note that you can setup macro security to low (there are registry settings
that you can set here).
ROOT:Local Machine
Key: Software\Microsoft\Office\11.0\Access\Security
Name:Level
Value:#00000001
The problem here is that this was working with a 2007 setup, so I not sure
it is a good idea to mess this up?
Perhaps my understanding is that you have only the ability to create a mde
from 2003? That would expain this issue (but you left out this detail, so I
can only speculate and guess as to this being the actual problem here).
The installing of access (full or runtime) is a rather large install and is
a major upgrade to that person's version of office running on the computer.
Keep in mind that just as many things can break and are just as problematic
when you install the runtime onto a target computer, as if you're installing
a full blown version of MS access (in other words, since the runtime and
full editon are compatible and buyers century the same thing, then all the
problems of installing multiple versions MS access on the same computer will
occur regardless if it is a full or runtime edition).
So, you want to be careful because if they're running other applications you
can really mess things up here.
Who, how and when did the accDR get there? I don't think you should just
overwrite and replace something without finding out what's happened and how
this happened in the first place?
It is not clear if you running a mix of 2007 and 2003 mahcines here? The
best approach in this case is to distribute a accDE for the 2007 people, and
a mde for the 2003 people.
Is this a split environment in which you are distributing front ends to each
computer (and they are linked to a common back file on a server?). You need
to inquire about this because you can't overwrite that accDr file in case it
has valuable or important customer data inside of that accDR.
By the way a accDR is useally a accDE, but it is simply re-named as a accDR.
(the "R" means that the application will run as if it was deployed to a
runtime installation, EVEN WHEN the users can the have the full eddition of
MS access 2007. So, that "R" can be the result of a file re-name manually,
or often that is what the 2007 package wizard does in this case.
You can do some testing, and if you have several users working with access
2003, and several other users working with 2007, then a good approach is to
test and distribute one version of access 2003 (a mde) to both sets of
users. This will usually will work quite well, I do recommend if you have
the possibility to distribute the appropriate version of the access front
end to the computers with the appropriate version of MS access (runtime or
full addition, it really does not matter).
If the your don't have control over this, nor do they not care about what
version of MS access, then simply install the access 2007 runtime on all the
machines, and you're done with a problem. In this case I do recommend that
you then always distribute an access 2007 version of your application.
Or if you're developing and are comfortable with 2003, then if you have the
2003 runtime, then use that for everybody.
Is just not clear why you have a mixed environment here. Some have 2003, and
some have 2007, but if you have the choice then try to unify this into one
version for everybody
