Can a Form "Forget" Its Objects

[JRB-Bldr]

I have a form which is pretty simple:
* 2 OptionGroups
* 2 Simple Grids
* 2 OLE Objects - 'oleFirstDate' & 'oleLastDate' Calendars
* 1 ComboBox
* 1 Command Group with 2 buttons

The OLE Calendars are Microsoft Date and Time Picker Control 6.0 (SP6).

With my OK.ClICK method I use the following code, so I assume that is where the error is occuring.

mcDay = PADL(ALLTRIM(STR(THISFORM.oleFirstDate.OBJECT.DAY,2)),2,"0")
mcMonth = PADL(ALLTRIM(STR(THISFORM.oleFirstDate.OBJECT.MONTH,2)),2,"0")
mcYear = STR(THISFORM.oleFirstDate.OBJECT.YEAR,4)
mcFirstDate = mcMonth + "/" + mcDay + "/" + mcYear
mdFirstDate = CTOD(mcFirstDate)

Most of the time these things all work together well.

But sometimes I get an error message indicating...
Unknown member OLEFIRSTDATE

Can the Form somehow "Forget" its objects?
How do I ensure that this type of error goes away?

As always, your advice and suggestions are most welcome.

Thanks,
JRB-Bldr

 

[alvechurchdata]

But sometimes I get an error message indicating...
Unknown member OLEFIRSTDATE

Is this happening in the form Load before the object has been created or in form.Unload after it's been destroyed?


Geoff Franklin

http://www.alvechurchdata.co.uk

 

[bborissov]

Did you have any problems with this:

WITH thisform.oleFirstDate.Object
     mdFirstDate = DATE(.Year, .Month, .Day)
ENDWITH

or even with this:

WITH thisform.oleFirstDate  && No OBJECT reference here
     mdFirstDate = DATE(.Year, .Month, .Day)
ENDWITH

I ask because I never worked with Calendar Control

Borislav Borissov

 

[JRB-Bldr]

No, my error log (from the error handler portion of faq184-4492) indicates that this error message is being thrown up during the execution of the OK.Click method.

The ONLY place within that method code where that OLEFIRSTDATE is referenced is the code shown above.

Thanks,
JRB-Bldr

 

[JRB-Bldr]

Boris - I have not tried it the way that you suggest.

I am currently following the method I found on the web for using that OLE object.

However, my problem is not the date conversion itself.
I assume (although I am not certain) from the error message
Unknown member OLEFIRSTDATE
that the problem is the Form's "knowing" about OLEFIRSTDATE.

And if the problem were with the OLE object's properties (DAY,MONTH,YEAR), then why would it work most times and not work some time?

I always initialize the both of the OLE Calendar Objects to a known good date ( DATE()-1 ) during the Form.Init method.

Thanks,
JRB-Bldr

 

[TamarGranor]

FWIW, I don't think you need to build the date that way. Try looking at the Value property of the OLE Control.

mdFirstDate = TTOD(ThisForm.oleFirstDate.Object.Value)

Tamar

 

[bborissov]

O, I see, What this gives you in error handler:
(I hope you use VFP8 or VFP9)

ASTACKINFO(laStack)
LIST MEMO LIKE laStack TO FILE lcError.TXT
MODIFY FILE lcError.TXT

Borislav Borissov