Re: Runtime Environment does not recognize functions
- From: "Alex Dybenko" <alexdyb@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 18 Feb 2006 12:07:47 +0300
Hi Doug,
very good addition about versions, this is quite important.
not sure that it is really required to have "the same location" for referenced libraries. from my experience - if library registered correctly - it does not matter there it physically stored. do you have other experience?
--
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com
"Douglas J. Steele" <NOSPAM_djsteele@xxxxxxxxxxxxxxxxx> wrote in message news:%23kBOv%237MGHA.2036@xxxxxxxxxxxxxxxxxxxxxxx
I'd go one step further than that, Alex.
On the developer's PC, determine the location of each of the referenced files, and determine the exact version of each.
Then, on the machines where it's not working, ensure that each of the referenced files are in the same location, and are the same version.
I have some simple code at http://www.accessmvp.com/DJSteele/AccessReferenceErrors.html that should help in the first part.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)
"Alex Dybenko" <alexdyb@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:esIJje5MGHA.4052@xxxxxxxxxxxxxxxxxxxxxxxI mean, that you have to look at reference at your developer's PC
there are 3 references, which always there, and installed with any access version:
Access
VBA
DAO or ADO
all others - you should either switch off, or take case installing it, if you really using
Also ADO - user should have same version installed, or at least higher
--
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com
"Jenn D." <JennD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:CE83A59C-3BC3-46E5-B7CB-9610AB2C9A21@xxxxxxxxxxxxxxxxYou can't open any VB code once you have installed the db on a clean
computer. The original db and packaged dbs on computers with Access work like
they're supposed to. The packaged db on a clean computer does not. You cannot
open a module in a packaged db... when packaging, it changes the mdb more or
less into an mde. Therefore, cannot open modules/code = cannot install
references!!! Also, I don't want the end-user(s) to have to install anything
extra. So... back to my question... is there a way to fix this in the
packaging process?????????????
--
Jenn D.
"Alex Dybenko" wrote:
Looks like some reference is missing. open any module, go to menu
tools-references. if you have a reference to some 3rd party activex
control - you have to install it. if you have reference to
word/excel/outlook -you have to be sure these are installed, or use late
bindings
--
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com
.
- Follow-Ups:
- Re: Runtime Environment does not recognize functions
- From: Douglas J. Steele
- Re: Runtime Environment does not recognize functions
- References:
- Re: Runtime Environment does not recognize functions
- From: Alex Dybenko
- Re: Runtime Environment does not recognize functions
- From: Alex Dybenko
- Re: Runtime Environment does not recognize functions
- From: Douglas J. Steele
- Re: Runtime Environment does not recognize functions
- Prev by Date: Re: Runtime Environment does not recognize functions
- Next by Date: Re: Runtime Environment does not recognize functions
- Previous by thread: Re: Runtime Environment does not recognize functions
- Next by thread: Re: Runtime Environment does not recognize functions
- Index(es):
Relevant Pages
|
Loading