Sure, Razzak, you can submit that request for me! I'm not sure in the
grand scheme of things if it should go high up on the list. We each have
individual ways of dealing with this issue and I'd rather your time was
spent on program enhancements and fixes.
Let's submit that as an enhancement request at RBG7 R:DCC.
I'm sure that R:Dream Team will consider that as a nice
feature in 7.5 and V-8 Turbo. Would you like me to have
the pleasure of submitting that request?
Bill D:
You're right! I knew I could document my forms in this matter, but I forgot
that I could actually modify the forms. Just like the good old DOS days of
editing sys_forms! Just had to remember to NOT have the "insert" key on!
>EDIT * FROM sys_forms3 WHERE sys_data CONTAINS 'karenscolumnname'
>Double-click on the sys_data "blob" cell.
>Press Ctrl-H, and in the "find" dialog, type karenscolumnname
As Marc says below, I have long ago stopped having individual eeps
on each control. I always have one eep per form (like CustEdit.eep)
and all my calls are to: CustEdit.eep USING 'print'. If code was common
between eeps, then I would decide whether it was easier to duplicate code
in each place (always with comments that "if you change something here,
also change it in <xxx>" or whether I have an external file called from
several eeps.
>I was thinking of having a BigEEP.apx file,
>and a Big RMD.apx file. These files would
>have hundreds of the smaller files in one BIG
>file . Then do Run xyz in BigEEP.apx. At
>least in the places RBW has that option.
>I am wanting to avoid keeping track of
>several copies of the same code and
>making changes in several places.
Thanks for the interesting discussion so far!
Karen
