r , 2010-05-30 15:38:39
I’m reading various data from an Access database with an ancient field
format (it used to be a mainframe app) that we are obliged to maintain. In
one of my earlier posts, I note that this database’s table is opened, parsed
(a number of string parsing operations are required to translate the data
into something easily used by Project e.g. multiple binary flags instead of
string enumerators for certain fields, translation of a strange date format
string into MS date format) with the parsed data loaded into the members of a
custom VBA class module, all within about 2 seconds.
The issue is then exporting it to MSP. I don’t see how reading from a loaded
class would be a bottleneck (though I’m willing to be told!), so I presume
the problem is writing to MSP.
The MSP fields I am currently writing to are:
I’ve taken the values of VBA.DateTime.Timer at the beginning of export of
each task, after the field values have been set and after the outline level
has been set.
The results are as follows:
MSP Hidden, Showdraw False – writing of data items 0.31-1.07s, outlining
MSP visible, showdraw true, no user interaction – writing of data items
0.24-0.63s, outlining 0.06-0.20s.
MSP visible, showdraw true, user scrolling down – writing of data items
<0.01-0.02s, outlining consistently <0.01s. Note that the above show my earlier ("gut feeling") timings for hidden MSP were wrong. I'd be interested to hear if the data movement is any slower for you when exporting data from Excel to Project (i.e. code resides in Excel). I'd also be interested to know if the workaround (continuous scrolling) works in either case. It's only the fact that the workaround works that keeps me searching for an elegant solution... I know the MSP MUST be capable of working more rapidly - I just don't know how to make it so! Regards, Dave.