Re: differences beween runtime and regular database, why do I get errors?
- From: "Albert D. Kallal" <PleaseNOOOsPAMmkallal@xxxxxxx>
- Date: Tue, 11 Dec 2007 18:14:45 -0700
"phleduc" <Ph.Leduc@xxxxxxxxxxxxxxxxx> wrote in message
news:uyWpYl6OIHA.5160@xxxxxxxxxxxxxxxxxxxxxxx
I think it might actually be reference issues. I kind of naively assumed
that the package wizzard would automatically rap up my dll's that are
referenced but perhaps at this point it seems like that might be the
problem
That is very likely your problem. Are these activeX controls, or standard
windows .dlls?
Standard dll's are run by declare a api in your code, where as activeX
(com) objects are used AFTER you register the com object (regsvr32.exe "path
name to your .dll). *after* you register a activeX object, you can then
set a reference in tools->references (in code editor). Note that you can
choose to NOT make a reference, and use late binding. YOU STILL MUST
register the object via regsvr32.exe on the TARGET machine to use the
object, *even* if you using late binding.
Do I have to attach them to my package one by one? What if they are
already present on my machine.
If your using standard .dlls, then you can place them in the same directory
as msacces.exe, or the system32 directory. Or, better yet, place then in the
same directory as your front end "mde", and use the windows loadapi to use
the dll's (this approach makes deployment much easier).
If they are activeX controls, like a 3rd party grid control, then you have
to
do two things:
1) make sure you have the developer edition of that control, since windows
3.1, activeX controls have a licensing system built in, and you simply can't
just copy
a ocx, dll com object to another machine, and regsvr32 it.
You MUST use the installer *and* also the developer editions of the
control.
2) once you have a legal edition of he activeX/com object on the target
machine, then you need to use a installer, or a script to register this
object.
The access 2003 package wizard has NO such ability. I suggest you use
something like inno which is free, and can deploy and register those activeX
objects, but
you have to make sure you have developer editions of those objects before
they will register correctly on the target machine.
treeview, listview, calendar, and 3 other acttiveX controls (that I can't
remember) ARE installed by default when you use the a2003 runtime.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@xxxxxxx
.
- References:
- Prev by Date: Re: Security Pop Up after automated installation of 2007 DB
- Next by Date: Re: Security Pop Up after automated installation of 2007 DB
- Previous by thread: Re: differences beween runtime and regular database, why do I get errors?
- Next by thread: Security Pop Up after automated installation of 2007 DB
- Index(es):
Relevant Pages
|