D
dp
Hi Everyone,
I have created a prototype application in MS Access. Each customer will be
able to commission us to customize the forms and reports according to their
needs. But the basis of the program will remain the same. Our company would
like to distribute this application using effective object oriented
programming techniques. However, I am having problems trying to understand
how accomplish separating the module code that relies a lot on VBA procedures
that I have created which weave in and out of database sql related code.
Also, the form modules that rely on event procedures.
I have absolutely no idea what to do if there were to be a bug. Most
applications use dlls to effectively distribute new code. I have separated
the front and back end and tried to create separate procedures for each form
event. We are also going to use VSTO to distribute the program.
Does anybody have any resources, books or otherwise or suggestions that I
can reference?
Thanks so much
I have created a prototype application in MS Access. Each customer will be
able to commission us to customize the forms and reports according to their
needs. But the basis of the program will remain the same. Our company would
like to distribute this application using effective object oriented
programming techniques. However, I am having problems trying to understand
how accomplish separating the module code that relies a lot on VBA procedures
that I have created which weave in and out of database sql related code.
Also, the form modules that rely on event procedures.
I have absolutely no idea what to do if there were to be a bug. Most
applications use dlls to effectively distribute new code. I have separated
the front and back end and tried to create separate procedures for each form
event. We are also going to use VSTO to distribute the program.
Does anybody have any resources, books or otherwise or suggestions that I
can reference?
Thanks so much