|
PureBytes Links
Trading Reference Links
|
Thanks for the response. And would appreciate a full view of your conversations
those moments when it is a less complicated issue. While I do not have much, if
any, positive to contribute, I do find this list a wealth of information and
knowledge that I can occasionally incorporate when I am able to fit into my
current level of knowing. When "it" is above me, but I have an interest, I
still have been exposed to something new and can build upon that. Your stuff
fits this description; I do not have a base, but read anyway. Doubt I am the
only one. And you are generous with splashing your knowledge and expertise
about, so please be aware that "it" goes much farther than just to whom it is
aimed, especially with background.
Please consider deleting identification and sending original.
Regards,
Dan
W Lake wrote:
> Hi Dan
>
> It's a complicated issue.
>
> 1. Some of the people who write are posters or ex-posters who are in to
> off-topic areas and don't want to be "disloyal" to a Metastock only
> configuration.
>
> 2. Some of the writers are non-posters i.e., lurkers who don't want to be
> known.
>
> 3. Others practice in what is considered "gray" areas in the computer
> industry and don't want to irritate the ethics of others, e.g., using a
> password generator to open locked programs. Or, changing the skin of a
> copywrited user application.
>
> 4. etc.
>
> Needless to say it's easier to just not include the original correspondence.
>
> ========================
>
> To others who wrote
>
> The "test" xll that you sent is only 683 KB. It contains 3 files. A dialog
> file with an "Excel Test Dialog" box to test free stack space.
>
> The second file is hex code. The third file is a version file.
>
> Sorry ... nothing here, but at least it opens easily like a dll. It can be
> edited to whatever you want, once you decide what you want to call. <G>
>
> The xla that you sent keeps all of the formulas on the work sheet of the
> xla rather than in the VBA code modules. Change the "IsAdd-In" to false to
> see the sheet and the formulas. Change it back to true to close the xla.
>
> I know that Hidden Markov's are a hot topic now and that lots of work is
> being done in that area, but I'm low man on the totem pole for this one.
> Sorry.
>
> Best regards
>
> Walter
>
> ----- Original Message -----
> From: Dan <dcash@xxxxxxxxxxxx>
> To: <metastock@xxxxxxxxxxxxx>
> Sent: Tuesday, February 06, 2001 11:57 PM
> Subject: Re: stuff
>
> > Walter,
> >
> > Your posts are always chucked full of great information and I only wish I
> knew
> > what the other side of this conversation, as an example, stated. You are
> > obviously answering someone specific on the list but since you usually do
> not
> > include the original, I am usually at a loss and miss out on another
> nugget of
> > your wisdom once again!
> >
> > I really do wish, fervently (hyperbole), that you would, as a matter of
> course,
> > hit the reply button, so I, we, would be able to benefit from both sides
> of the
> > exchange.
> >
> > Respectfully (really),
> >
> > Dan (part of the ten percent that is always the last to hear)
> >
> >
> >
> > W Lake wrote:
> >
> > > Hi
> > >
> > > In the workbook you might want to look for hidden sheets and hidden
> columns.
> > > In this case there are many hidden columns filled with in-cell code and
> > > named ranges. One sheet has over 100 hidden columns. Watch out for text
> that
> > > is the same colour as the background. Use the map that you mentioned to
> > > find and change the colour of the fonts.
> > >
> > > The VBA code makes regular references to the named ranges in the hidden
> > > columns. So if you want to modify the code you will need to see the
> in-cell
> > > code and named ranges that you are referring to.
> > >
> > > Delete the surface "junk" boxes and record or write your own code for
> the
> > > subs/macros that are insufficient.
> > >
> > > The modules are isolated so debugging is very easy if you comment your
> > > changes and make notes in text boxes on each sheet that you change.
> You'll
> > > learn a lot from the workbook.
> > >
> > > An xll is different from a dll so it may not be visible in the same way.
> Let
> > > me know if you have any luck.
> > >
> > > Best regards
> > >
> > > Walter
> >
> >
> >
> >
> >
--
mailto:dcash@xxxxxxxxxxxx
Kibosh spam: http://spamcop.net/
Dan
|