|
-
Nov 8th, 2001, 04:09 AM
#2
Hyperactive Member
If the High-Power Server capable of supporting VB DLL's ? I.e it's not a Linux/Unix/somsuch machine then to move to DCOM is simple.
All you need to do in install/deploy your DLL to the new server (not forgetting to configure your database connection of your server etc !!). Open the Client VBP and make a Networked Path reference to the DLL on the new server & re-deploy the client.
Of course, things to consider when deploying the DLL are any dependencies the DLL may require, connections to Databases etc etc, the load the DLL will have to take... It really depends upon how tight you coded your DLL and what it's for. But assuming your Error Handling etc follows COM rules etc then there should in theory be No problem.
FATBOYPEE
Last edited by FATBOYPEE; Nov 8th, 2001 at 04:53 AM.

Best Bar.....
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|