nina2kool
Aug 24th, 2001, 10:58 PM
Hello All,
I have developed a VB6 application to query databases and then store the query results in a temp table in SQL Server so that report can be generated. The application is working. But it is slow and it ties up the user's computer. I like to move the processing routines off the standard exe project to an ActiveX DLL project, and run it asynchronously.
My knowledge on DLL is quite limited. I know how to create the DLL project and how to reference it and use it. But I don't know how to design the DLL...... things like what codes should be in it? Right now, my processing routines call other subroutines within the project, if I move the processing routines out to the DLL project, what should I do with those calls? Is it right for a DLL to call a subroutine in the standard exe project? I seriously doubt that, but I don't know how to correct it. Should I move
those subroutines over to the DLL also?
Is it necessary to create all those Property Let/Property Get subroutines, and how?
As I mentioned earlier, I am storing the query results in a temp table which exists globally ONLY within the standard exe project. Once I leave that and go to the DLL side, I lose the temp table object. How can I retain the object?
And finally, how to set up the DLL to run it asynchronously so that I can free up the user's computer?
Any help will be very much appreciated.
I have developed a VB6 application to query databases and then store the query results in a temp table in SQL Server so that report can be generated. The application is working. But it is slow and it ties up the user's computer. I like to move the processing routines off the standard exe project to an ActiveX DLL project, and run it asynchronously.
My knowledge on DLL is quite limited. I know how to create the DLL project and how to reference it and use it. But I don't know how to design the DLL...... things like what codes should be in it? Right now, my processing routines call other subroutines within the project, if I move the processing routines out to the DLL project, what should I do with those calls? Is it right for a DLL to call a subroutine in the standard exe project? I seriously doubt that, but I don't know how to correct it. Should I move
those subroutines over to the DLL also?
Is it necessary to create all those Property Let/Property Get subroutines, and how?
As I mentioned earlier, I am storing the query results in a temp table which exists globally ONLY within the standard exe project. Once I leave that and go to the DLL side, I lose the temp table object. How can I retain the object?
And finally, how to set up the DLL to run it asynchronously so that I can free up the user's computer?
Any help will be very much appreciated.