Click here to Skip to main content
15,881,248 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
Hello All,

I have a question:
I have 2 applications (say X & Y). Both the applications use a OCX library file to perform some FTP functions. The only difference is that 'X' is a separate application which calls this OCX file to perform the FTP tasks while in case of 'Y', the OCX file is embedded directly in the project solution(Its the part of the 'Y' application).

When FTPGetFile() is called in the OCX file from 'X' application, to transfer a specific file; the FTPGetFile() takes 40 Seconds.
But when the same FTPGetFile() is called from the same OCX file from 'Y' application, to transfer the same file; it takes 20 Seconds.

So, my question here is what makes the FTPGetFile() method to take more time when called from 'X' application and take less time when called from 'Y' application ?
Is there something in the way OCX is linked to the 2 applications? I mean, 'X' tries to load the OCX file while 'Y' has the same OCX file directly embedded in its solution. Does this makes any difference in the way Windows loads the OCX file and perform the FTP function.

NOTE: Both the 'X' & 'Y' application use the same OCX file. Both call the same FTPGetFile() method & try to transfer the same file. Everything is common except the way OCX is loaded by the applications.
The applications are developed in VB6 & C++

Please share your views on this problem.

GUYS PLZ THROW SOME LIGHT ON THIS...ANY KIND OF IDEAS WILL BE HIGHLY APPRECIATED

Thanks & Regards,
Dinesh
Posted
Updated 27-Sep-13 4:15am
v3
Comments
Sergey Alexandrovich Kryukov 27-Sep-13 10:18am    
There can be million reasons for that. Not enough information.
—SA
[no name] 27-Sep-13 10:23am    
Thanks SA for quick response...
I really need some valid points for this situation.
Please let me know what additional information you want to come up with some valid reasons.
Will there be something w.r.t the way the OCX was built with the applications (Or) the way OS loads the OCX in memory while invoking the applications using the OCX.
Thanks
Sergey Alexandrovich Kryukov 27-Sep-13 10:27am    
I don't want any, you do. :-) I generally don't understand how it's possible to torture yourself with VB6. Any specific reasons for that?
—SA
[no name] 27-Sep-13 10:29am    
:) Yes, true. We are supporting a legacy application 7+ yrs old. That's the reason we are still stuck up with VB6.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900