Am working on a program that for the first time involves tens of thousands of active files instead of tens of thousands of active members.
Also for the first time I'm making use of the API--and objects in general--due to the versatility they afford above the intrinsic file operations of BASIC.
But when I have altered code from BASIC commands to OOP during "development" it [seems] that speed decreases. The HDD activity led would [seem] to concur as the ordinarily buries it while the API results in flashing.
I've searched here and elsewhere to find no answer but I suspect that the intrinsic file commands operate at a lower level not involving the API.
If, instead VB does utilize the API for its file operations then it must be up to me to optimize the code and system utilization for speed.
Also for the first time I'm making use of the API--and objects in general--due to the versatility they afford above the intrinsic file operations of BASIC.
But when I have altered code from BASIC commands to OOP during "development" it [seems] that speed decreases. The HDD activity led would [seem] to concur as the ordinarily buries it while the API results in flashing.
I've searched here and elsewhere to find no answer but I suspect that the intrinsic file commands operate at a lower level not involving the API.
If, instead VB does utilize the API for its file operations then it must be up to me to optimize the code and system utilization for speed.
