I'm working on a complex 3 thier application (using MS MTS).
A part from MTS classes, at the beginning of development I decided to divide the client application into components:
- an application VB project where to store application logic & UI (d.e. forms)
- a DLL ActiveX VB project (to share with other applications) where to store standard objects & functions (general code library)
- an ActiveX Control VB Project (to share with other applications) where to store ActiveX input controls (textbox, date & time, checkbox)
- a DLL ActiveX VB project (to share with other applications) where to store the application UI framework (something like MS Outlook UI....menu & toobars, data-explorer and data-views)
That is seems to be a good plan but how can I share application istance resources between objects without have to pass hundreds of parameters each time I need make a
call that refer to another ActiveX/dll method?
Take for example the variable that store the MTS Server name.
When the application boot (application VB project) gets the server name from the registry; each time I need to make a call to MS MTS methods I need to use this parameter.
No problem on the application VB project itself but how can I pass the server name to the other ActiveX components without have to use parameters or properties?
I mean, is there a way to put in memory a persistable class where each component can get all application istance resources (connection parameters, user info, app. status)?
Is there a way to do this? If yes, is this a good idea/approach?
A part from MTS classes, at the beginning of development I decided to divide the client application into components:
- an application VB project where to store application logic & UI (d.e. forms)
- a DLL ActiveX VB project (to share with other applications) where to store standard objects & functions (general code library)
- an ActiveX Control VB Project (to share with other applications) where to store ActiveX input controls (textbox, date & time, checkbox)
- a DLL ActiveX VB project (to share with other applications) where to store the application UI framework (something like MS Outlook UI....menu & toobars, data-explorer and data-views)
That is seems to be a good plan but how can I share application istance resources between objects without have to pass hundreds of parameters each time I need make a
call that refer to another ActiveX/dll method?
Take for example the variable that store the MTS Server name.
When the application boot (application VB project) gets the server name from the registry; each time I need to make a call to MS MTS methods I need to use this parameter.
No problem on the application VB project itself but how can I pass the server name to the other ActiveX components without have to use parameters or properties?
I mean, is there a way to put in memory a persistable class where each component can get all application istance resources (connection parameters, user info, app. status)?
Is there a way to do this? If yes, is this a good idea/approach?