Can anybody help with "strategic planning" on this?
I am working on a VB5 DAO accounting application which, like most
accounting systems, has a customer list. I am noticing that there are
already four major places in the program where I need to go to the
disk to get a customer record, and go back and write it back again.
I don't want to maintain the same code in four places, every time the
Customer definition changes. Furthermore, I want the code to be
upgradable from JET 3.5 to ODBC or ADO some day...
QUESTION 1- Does it make sense to have a class module (call it
clsCustomerIO) with methods ReadCust and WriteCust?
Q.2- My brain is telling me to define a "user defined type" which
would be returned by this ReadCust (or processed by WriteCust)
subroutine. But I seem to recall I shuld be making an ActiveX or DLL
with publicly exposed property lets and property gets? Is that
Q.3-- Is this puppy going to run slower if I do this? two of the four
places, I'm looping thru the customer list to perform tasks like
applying logic to synchronize the customer list with external
software. Will the loop run significantly faster if I code it the
"old fashioned way" directly accessing the recordset in the loop?
Any help much appreciatd,