Client-side Components

[Yazster]

Hi, I'm hoping someone can help me.

I have a large system (designed using 3-tier architechture) that I'd like to bring to the web. Data services, business logic and UI have all been built using VB6. At this point, all business logic and UI components are registered on each client's machine. So, here's my problem:

Due to company policy, I have web space allocated to my application, as well as ASP enabled and frontpage extensions loaded. Problem is, I'm not permitted to register components on the web server. All I would have to do is bring my .DLL files to the server, and all the functionality would be available, but red-tape prohibits this.

Is it possible for me to use the components registered on each client's PC using ASP? From what I've seen, components must be registered on the web server to be used. I'm hoping this is not the case....

Any help would be greatly appreciated.

Thanks,
Yazster

 

[Tarwn]

Unfortunatly that is the case. Since ASP processes only on the server, it does not have access to the client machines registered dlls or even text files.

If you want to outline a little more in depth what you are trying to do, someone else may have run into the same problem at some point and could offer advice.

Sorry to be the bearer of bad news,
-Tarwn --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
For my next trick I will pull a hat out of a rabbit (if you think thats bad you should see how the pigeon feels...)

 

[Yazster]

Hi Tarwn,

Thanks for the reply.

Well, here's what I'm trying to do:

We have a very sucessful application that has been in existence for about a year. It basically runs various corporate queries from over 45 different databases. It's basically a VB6 MDI-Style application, deployed to approx. 250 users.

So last week we heard the news that the system will be deployed to 400 more users, and we've been requested to design a web-version of the application, so we wouldn't have to deploy it anymore.

We basically knew this would happen, which is why we designed the system in a 3-tier platform independent environment. Basically, all the functionally is located in the business logic (ActiveX .DLLs) and data services (ActiveX .EXEs)

Which means we can easily modify this system to work with the web, as long as we have access to our components! This, is the problem. This would be a non-issue if we could simply register our components on the web server and design the front-end using ASP. However corporate politics (a whole other story) is making this difficult.

Basically, I need to have a web environment, using ActiveX DLLs located on each client's PC. My first thought, create a DHTML project in VB6. This works fine, however deploying it seems to be as much of a pain as deploying a full-scale local application.

Any ideas?

 

[MrGreed]

Yaster,

Your correct, your solution and the ones avaibale will still require each user to have the components on their machines. I know you said there are "Management" problems, but if they want it on the web so you don't have to issue each user the components then they will have to let you place your dll.s on the webserver. That is the entire point of having a webserver. "did you just say Minkey?, yes that's what I said."

MrGreed