This is because some other components you may have added to your project may
be referencing this dll... this may also happen if you are using databound
controls
--
Gaurav Creations
> My project has a reference to Microsoft Data Formatting Object Library, I
> didn't add it?? I can remove the reference, recompile without a problem and
[quoted text clipped - 5 lines]
> Regards,
> Chuck Faranda
Chuck Faranda - 31 Aug 2004 12:12 GMT
This is what is so strange, I do not see anything that would use it??

Signature
Regards,
Chuck Faranda
> This is because some other components you may have added to your project
> may
[quoted text clipped - 16 lines]
>> Regards,
>> Chuck Faranda
Gaurav - http://www.gauravcreations.com - 31 Aug 2004 13:03 GMT
try looking for dependencies using 3rd party tools like exe depender
http://www.freewareweb.com/cgi-bin/archive.cgi?ID=179
--
Gaurav Creations
> This is what is so strange, I do not see anything that would use it??
>
[quoted text clipped - 18 lines]
> >> Regards,
> >> Chuck Faranda
"Chuck Faranda" <spam@ccdastro.net>'s wild thoughts were
released on Tue, 31 Aug 2004 06:13:05 -0400 bearing the
following fruit:
>My project has a reference to Microsoft Data Formatting Object Library, I
>didn't add it?? I can remove the reference, recompile without a problem and
>save the project. However, when I reopen the project the reference returns,
>any ideas on what is happening are appreciated.
You have accidentally set the DataFormat property of a label
control or some other control.
Changing this will cause this reference to be added
automatically.
You'll have to find the control with the problem and you'll
have to remove the control and add a new one to replace it
(IIRC you can't reset the property - anyone know
differently?)
Jan Hyde (VB MVP)

Signature
Give a man fire and he is warm for the day.
Set him on fire and he is warm for the rest of his life.
[Abolish the TV License - http://www.tvlicensing.biz/]
Chuck Faranda - 31 Aug 2004 13:26 GMT
Thanks Jan, I will search for that.

Signature
Regards,
Chuck Faranda
> "Chuck Faranda" <spam@ccdastro.net>'s wild thoughts were
> released on Tue, 31 Aug 2004 06:13:05 -0400 bearing the
[quoted text clipped - 19 lines]
>
> Jan Hyde (VB MVP)
Don@home.com - 31 Aug 2004 13:36 GMT
>"Chuck Faranda" <spam@ccdastro.net>'s wild thoughts were
>released on Tue, 31 Aug 2004 06:13:05 -0400 bearing the
[quoted text clipped - 17 lines]
>
>Jan Hyde (VB MVP)
A couple years ago I got bitten by this bug with a control array of all
things...
Here's how I took care of the problem...
In a Text Editor, ie: NotePad, load the Form Code, *.frm file, and look for the
following-->
VERSION 5.00
Begin VB.Form Form1
Caption = "Form1"
ClientHeight = 3135
ClientLeft = 60
ClientTop = 405
ClientWidth = 4680
LinkTopic = "Form1"
ScaleHeight = 3135
ScaleWidth = 4680
StartUpPosition = 3 'Windows Default
Begin VB.Label Label1
Caption = "Label1"
BeginProperty DataFormat <<<<<<<<<Starts Here!!!
Type = 1
Format = ""
HaveTrueFalseNull= 0
FirstDayOfWeek = 0
FirstWeekOfYear = 0
LCID = 1033
SubFormatType = 0
EndProperty<<<<<<<<<<<<<<<<<<<<<<Ends Here!!!
Height = 525
Left = 1740
TabIndex = 0
Top = 1320
Width = 1245
End
End
Attribute VB_Name = "Form1"
Attribute VB_GlobalNameSpace = False
Attribute VB_Creatable = False
Attribute VB_PredeclaredId = True
Attribute VB_Exposed = False
Option Explicit
If I remember correctly all I did is delete the above lines and that was
that....
I know, I know.... M$'s no escape clause...
Have a good day...
Don