I'm having this problem where my VC++5 resource file keeps growing in
size. It started out as 40K (which is reasonable) and is now over 12M.
There are no icons, bitmaps, etc. in the resource file.
I've looked in the resource file and the culprit section is as follows:
IDD_PROGCFG_DIALOG DLGINIT
BEGIN
IDC_MSFLEXGRID1, 0x37a, 274, 22
0x0024, 0x0000, 0x0037, 0x0032, 0x0045, 0x0036, 0x0037, 0x0031, 0x0032,
0x0030, 0x002d, 0x0035, 0x0039, 0x0035, 0x0039, 0x002d, 0x0031, 0x0031,
[...]
0x0000, 0x0000, 0x0000, 0x0000, 0x0000, 0x0000, 0x0000, 0x0000, 0x0001,
[...a few thousand lines of zeroes removed...]
0x0000, 0x0190, 0x4244, 0x0001, 0x4d0d, 0x2053, 0x6153, 0x736e, 0x5320,
0x7265, 0x6669, 0x746c, 0x0000, 0x0000, 0x0000, 0xa029,
0
END
It seems to get bigger every time I change something in the msflexgrid
control. Of
course, this has started to get very annoying as it takes a long time to
save and
compile the resource file. I've tried removing all the lines containing
zeros (which
drops the file size to 50K or so), but Visual Studio starts complaining
and/or the
msflexgrid control doesn't work (or the program crashes).
Anybody have any ideas as to what's causing this and how to stop it??? I've
looked in all the manuals, MS knowledge base, etc. and haven't found
anything
that seems to address this problem. Please HELP!
My environment is Win98, VC++5.0 with all service packs installed. The
msflxgrd.ocx file is version 5.00.3714 (jan 14/97).
Thanks,
-paulo
--
Email address modified to reduce spam. Remove the 'X' to respond.
BEGIN
CONTROL "",IDC_MSFLEXGRID1,
"{6262D3A0-531B-11CF-91F6-C2863C385E30}",WS_TABSTOP,17,
19,122,133
END
Yours doesn't look anything like that. Seems like it is not related
to the flexgrid control, but rather to the rc file (so there won't be
any kbase for the control). My best advice would be to close the
project, delete the APS file, and reload everything. This file is what
Devstudio uses to generate the RC file. I have seen enough of these
kinds of problems crop up that I believe this file gets corrupted and
causes bizarre behavior. - Doug S.
There's a Knowledge Base article on it, but I don't have the ID handy for
it, sorry.
I believe the Knowledge Base's solution was to simply delete the control
from the form, then re-add it back in. (Unfortunately, you lose all your
changes, but it DOES get rid of all the junk.)
HTH
Reginald Blue | Opinions expressed here do not
Natural Language Understanding | necessarily represent those of
Unisys Corporation | my employer.
|-------------------------------
| My email address is wrong, you
r...@NOSPAM.trsvr.tr.unisys.com | need to remove the obvious.
Douglas Sutherland wrote in message
<36026C0D...@Spam-this-Kesmai.com>...
Hmm, I tried to search support.microsoft.com for anything with "flexgrid",
"msflexgrid", "flex", etc. and didn't get any matches. If you do know the
ID I'd really appreciate getting it.
>I believe the Knowledge Base's solution was to simply delete the control
>from the form, then re-add it back in. (Unfortunately, you lose all your
>changes, but it DOES get rid of all the junk.)
Tried it and it works. Thanks!
I guess the RC entry that I quoted in my original article is used for
storing the
control's properties, in some custom (ie, control-defined) way. The control
must be messing up when trying to update this section.
-Paulo
Looks like I was mistaken. I can't find any reference to a KB article
anywhere on this topic.
Arguably there SHOULD be an article, but I can't find it.
Sorry about that, (but at least you have the solution now.)