Wrox Programmer Forums
|
VB Components Issues specific to components in VB.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the VB Components section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old July 21st, 2003, 04:21 PM
Registered User
 
Join Date: Jul 2003
Posts: 4
Thanks: 0
Thanked 0 Times in 0 Posts
Default OCxs

Hi,

I am having trouble with ocxs and dlls.

I have broken my monolithic app into dlls and ocxs. However, when I rebuild an OCX or change the location of the project, the project fails to load. I see that the project refers to a hard coded location and refers to a registry entry.

Is there a simple way around this?

Any help appreciated.

ps.

I broke the app into seperate dll.ocxs because I get a "out of memory" while attempting to build the monolithic app.

stef
 
Old August 29th, 2003, 03:14 AM
Authorized User
 
Join Date: Jul 2003
Posts: 10
Thanks: 0
Thanked 0 Times in 0 Posts
Default

hi,

     I understood ur problem. Here u can solve ur problem by a way.
U copy ur components to a directory to C Drive.Your register from there.

Then even if you change the location of ur project, your dlls will not give any problem. Because of this reason only users register their components in system32 folder(Windows system folder). Then threre will not be any problem with ur application location.

I think this could help u:)

Bye
Veerendra Kumar


B.V.Kumar









Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.