somes questions

vubinhsg · #1 (**permalink**) April 14th, 2005, 09:03 AM

I have some questions concerning about the Access 2002.
In the Northwind sample, the form Employees contains the
Sub Form_Current()
………..‘The others lines
and then the line
Me![ImageFrame].Picture = fName
End sub

!!!This Property isn’t like any other control like combobox, textbox etc… I mean is it right that the control [ImageFrame].Picture search for the filename before. If this filename doesn’t exist it will not do the line Me![ImageFrame].Picture = FName above?

The Form_RecordExit doesn’t occur at any time

Other question
I try to enter a value to a date data type like this
When I type “29/2/2005” I have an error msg
but “29/2/05” give me another date “05/2/2029” or “31/4/05” give me “05/4/1931”

for these “29/2/2005” and “31/4/2005”, the Access’ OnError event catches them but “29/2/05” and “31/4/05” will be changed before the control’s BeforeUpdate event
I catch the control’s BeforeUpdate event in combining with the control.Undo but this occurs after the form’s OnError. So I have some wrong results after the undo method.
Can you show me a solution? Thank you.

rjweers · #2 (**permalink**) April 14th, 2005, 08:08 PM

If you set the image to a filename that doesn't exist, what do you think is going to happen? My bet would be that Access is going to report an error that the file could not be found. So I would say that you want to see if the file exists before you try to use it (your code snippit doesn't suggest that the file is checked first).

Clearly the date is being interpretted. I'm not sure why your dates are accepted in what appears to be YY/DD/MM format.

I would suggest that you not use the OnError event when the field the error is associated with is a date field but do your own editing in the BeforeUpdate event.

I've never used the OnError event of the form. Not sure why I would want to.

Randall J Weers
Membership Vice President
Pacific NorthWest Access Developers Group
http://www.pnwadg.org

vubinhsg · #3 (**permalink**) May 1st, 2005, 05:19 AM

yes i have tried with the BeforeUpdate event to catch the text and test before it save to record but if you type a value of date like 29/2/05 this will be changed to 5/2/2029 and saved to the OldValue Property of this Control. then the BeforeUpdate event shows my msg and does the DoCmd.Undo to this Control but the OldValue now is 5/2/2029, not the original OldValue. thanks so much

rjweers · #4 (**permalink**) May 1st, 2005, 12:23 PM

Sorry, I didn't understand your explanation about what was happening with the BeforeUpdate and Undo.

Not that this matters to you and I'm sure this has something to do with my system's date format settings. But if I type 29/2/5 into a date field, I get:

DateField.OldValue = 2/5/2029
DateField.Value = 2/5/2029
DateField.Text = 29/2/5

I assume that means the when you use the BeforeUpdate event to validate the format, you should look at .Text to see and edit what the user typed.

The Undo does give crazy results. Why does Access set the OldValue to garbage? Must have something to do with the fact that Access is aware that the field is a date field? Whatever!!!

Sorry, but it looks like you'll have to do things the hard way. You could try this code in the module of the form:

Code:

Dim varSampleFromDate As Variant
Dim blnSampleFromDateBad As Boolean

Public Function MyDateValidation(pvarDate As Variant) As Boolean
' NOTE: Undo won't work if validation occurs in the BeforeUpdate event
'       because the OldValue of the field gets set according to the bad
'       date that was entered.
If IsNull(pvarDate) Then
    MyDateValidation = True
Else
    If pvarDate = "29/2/5" Then ' validate date format
        MyDateValidation = False
    Else
        MyDateValidation = True
    End If
End If
End Function

Private Sub SampleFromDate_BeforeUpdate(Cancel As Integer)
blnSampleFromDateBad = MyDateValidation(Me.SampleFromDate)
End Sub

Private Sub SampleFromDate_Enter()
blnSampleFromDateBad = False
varSampleFromDate = Me.SampleFromDate
End Sub

Private Sub SampleFromDate_Exit(Cancel As Integer)
If blnSampleFromDateBad Then
    blnSampleFromDateBad = False
    Me.SampleFromDate = varSampleFromDate
    Cancel = True
End If
End Sub

Of course, depending on how important that date is, you could just let the bad date be recorded. Hopefully, users will get used entering dates properly.

rjweers · #5 (**permalink**) May 1st, 2005, 12:29 PM

Come to think of it, you could just put the date validation in Exit, then you wouldn't need blnSampleFromDateBad or the BeforeUpdate event.

Change the Exit event to:

Code:

Private Sub SampleFromDate_Exit(Cancel As Integer)
If Not MyDateValidation(Me.SampleFromDate) Then
    Me.SampleFromDate = varSampleFromDate
    Cancel = True
End If
End Sub

vubinhsg · #6 (**permalink**) May 8th, 2005, 04:31 AM

thanks for your help. this made me some experiences. but i have found the reason why for the problems (29/2/05) of date type control. finally, you could turn the autocorrect property of the controls who data type is date, to NO then it is solved.

by the way, if you can tell me why when i try to insert an expression to a textbox control on report. this doesn't work correctly. i tried also to create an unbound textbox then attach this =trim([address]) but this shows #error? or #name? on normal view or printpreview

need your help
VB

rjweers · #7 (**permalink**) May 8th, 2005, 09:54 AM

Didn't think of that autocorrect. That was a good find.

Since the text box question isn't related to the book, you should go ahead and ask it on the following forum:

http://p2p.wrox.com/forum.asp?FORUM_ID=5

Need to download code?

Navigation