begging for hints on 2 questions:

1: i did a little experimenting on xl97 formatting.

saving an empty worksheet results in a 13 kb file
saving a worksheet with the ENTIRE column marked with a different
color than default will result in 14 kb filesize (a mere 500 bytes
overhead compared to the empty file), but marking every SECOND column
with a single different color blows the file up to 1094 kb. evidently
a result of object orientated programming, which adds 16 bytes to the
individual object "column" resp. "cell" (strangely also to the
"unchanged" cells remaining in the default color. i assume, that excel
nevertheless assigns specific code to these cells priorly undefined)

so: do i have to assume, that excel assigns object code to a cell,
which remains the default, but is expressively assigned the default ?

to keep file sizes as small as possible: where can i get a hint, by
how many bytes excel files increases in size by special objects? do
all cell properties always have 16 bytes size/cell? or are there
exceptions? for example: how many bytes are used by conditional
formatting of a certain range ? some might argue, that in times of
100s of megabyte RAM this isn't a relevant question any more, but the
files from this special project might get real large and for certain
reasons i'm bound to spreadsheets the common user is accustomed to.


2: atpvbaen.xla

what is the use of GETMACROREGID(function) ?
where do i get the info for the correct calling convention from this
add-in without the proper password (which again raises the question,
why ms programmers are such fans of wildlife ;-))? )

vba-help does not include calls like hex2bin or bin2oct. do i overlook
any readme or hlp-file ?

totally happy with some useful links...

klaus