[AccessD] Data Types (was - Global Variable)

>Recalling that whole fiasco reminds me that nothing I do is so important
that I should try to improve the speed above and beyond that  of the
compiler(interpreter), I should just write code that is maintainable. Thanks
for the kick in the (memory) pants!

That is an important point.  Code should be written using "best practices",
then IF and WHEN bottlenecks are found, "tricks" can be used to speed things
up.  We have all seen code written by the idiot whose sole concern is speed
and whose code is unreadable, let alone maintainable.

John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Bartow
Sent: Thursday, May 19, 2005 9:01 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Data Types (was - Global Variable)


This brings back a lot of old memories from my C class. It was night school
taught by a guy who did equipment controller programming for IIRC Plexus.

He spent a lot of time teaching us how to write very optimized code which
unfortunately, when completed, no one could read without rediagramming it
all.

Recalling that whole fiasco reminds me that nothing I do is so important
that I should try to improve the speed above and beyond that of the
compiler(interpreter), I should just write code that is maintainable. Thanks
for the kick in the (memory) pants!

John B.


John W. Colby wrote:
In the end, all that level of stuff is handled by machine code.  The VB
required to deal with it is created by an interpreter, which is in turn
created by a compiler.  That compiler has optimizations which will do it's
best to pack memory into words etc.  

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com