Indeed.  The *.frx files mostly contain the property bag information.
Expect them anytime you set a properties on a property page.  If you have
trouble sharing them (which may happen with some 3rd party "operating
systems" that fail to automatically recognize the file type, try this:  go
to the property page for all of the *.frx in your project which are to
acccompany a rollout, and mark them READONLY using windows explorer.  This
is NOT a god idea to leave the *.frx READONLY on your development computer
as it would prevent them from being overwritten should you change properties
of something on a form which results in a change to one of the *.frx files
(which also reside on your development computer in the same location as your
source files usually).

RWA

----- Original Message -----
From: "Marco Straforini" <marco.straforini@c...>
To: "professional vb" <pro_vb@p...>
Sent: Tuesday, August 20, 2002 3:40 PM
Subject: [pro_vb] Re: .frx files


> Dear Alistair,
>
> it is not true that VB can store everything in the frm file.
> The frm is strictly text only, thus everytime you add an image
> to a picturebox (for example) the image itself is stored in
> the frx file, and in the frm file the image property of
> the picturebox points to an address in the corresponding frx file.
>
> Bottom of the story is, when you add a project to SourceSafe *OR*
> you modify a frm file so that it needs an frx, you have to add
> the frx in SourceSafe as well.
>
> Sometimes you have to do the opposite: you add an frx to SourceSafe
> and than you modify the frm so it does not need the frx anymore,
> so you have to remove the frx (if you care) from SourceSafe.
>
> The best way to accomplish this is to use SourceSafe directly from
> the VB IDE environment. VB knows when one form need an frx, so when
> you select 'Add to SourceSafe' the frx is added automatically.
>
> A trick I use is to open an explorer, go to the project folder
> and select Search..., and in the search options I select all
> the *.frm files containing the frx string. I was thinking to write
> an add-in to do it automatically but I think I need more time to
> write the add-in than doing the search by hand.
>
> I hope I was clear enough,
>
> Regards,
> Marco
>
> > I am having problems with .frx files :
>
>
> ---
> Visual C# - A Guide for VB6 Developers
> This book will make it easy to transfer your skills
> from Visual Basic 6 to C#, the language of choice
> of the .NET Framework.
> http://www.wrox.com/ACON11.asp?ISBN=1861007175&p2p0059
>