Re: auto-REregistering VB6 components?
- From: "Ralph" <nt_consulting64@xxxxxxxxx>
- Date: Sat, 2 Dec 2006 19:26:48 -0600
"javelin" <google.1.jvmail@xxxxxxxxxxxxxxx> wrote in message
news:1164995877.646063.166330@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Ken, you're obviously used to doing things the manual way, whichCompatibility
results in a greater level of knowledge (usually ) and control. I hope
to get there some day, but I need a solution to this problem for now.
I'd be curious to know where your components appear under in the
components manager. I thought you were required to put them under some
application package.
Ken Halter wrote:
"javelin" <google.1.jvmail@xxxxxxxxxxxxxxx> wrote in message
news:1164911728.007909.118720@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I checked the project properties, and it is set to Binary
longfor version compatibility. I am new to creating components, and was
told I should simply delete the existing registry entry for the
component, then remake the component, and reregister it. This is a
Thisprocess, because I have to select the component package in the
component manager, uncheck the "Enforce access checks for this
application", then re-add the component, then set it's security tab
roles manually, then enable object construction (under the activation
tab) and change the constructor string for the database connection. I
have to do this on the DEV system, the testing system and the
production system, each having their own username/password combo.
thisobviously gets old after the 10th or 12th time that day.
Thanks for any additional input.
hmmm... I've never (ever) used that component manager for anything...
hopefully, someone that has experience with it will pop in and add to
involvedthread.
Personally, I just build the components and when they're ready for "the
world", I place them in a public folder on the network. No managers
<g>
I am likely that one person that Ken is talking about that uses the Visual
Component Manger.
The key to the Component Manger is that it manages "Published Components"
that are expected to be shared among multiple projects and multiple
programmers.
The key to "COM" is once an interface is "published" the interface doesn't
change.
Therefore, you don't use the Component Manger for anything that isn't set in
stone. To replace a component, you need to create a new one. (different
name, etc)
hth
-ralph
.
- References:
- Re: auto-REregistering VB6 components?
- From: javelin
- Re: auto-REregistering VB6 components?
- From: Ken Halter
- Re: auto-REregistering VB6 components?
- From: javelin
- Re: auto-REregistering VB6 components?
- Prev by Date: Re: auto-REregistering VB6 components?
- Next by Date: Recordset Data Type
- Previous by thread: Re: auto-REregistering VB6 components?
- Next by thread: Re: auto-REregistering VB6 components?
- Index(es):
Loading