>
>This is probably the most important suggestion. I lose the most speed when the (codebook based) framework start running lots of methods that I know very little about. I cut out all of the DBCX-based verification because that was causing I/O in simple situations that didn't need that complexity.
That's one reason I've never gone with a commercial framework.
>
>>- Get rid of all m.Var on the left side of an assignment (m.MyVar = 3)
>
>I don't understand this. Are you saying, use the syntax:
>
>store 3 to MyVar
>
No.
m.MyVar = 3
is 3 times slower than
MyVar = 3
I've tested this in every version since 2.0 and the results are consistant. Some people argue that putting m. on the left-hand side makes it clear that it is a variable and will make sure that a variable is used instead of a field. This agruement doesn't hold water. You can't use a field on the left side of an equals.
>(I never use the M. prefix because I always have a scope letter on my variables that differentiate them from table fields.)
>
>Peter
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer