Form Event "On Save" Help

[twwtc]

I am trying to have an email sent to the owners (2) when we sell an item, with a report as a attachment (pdf).

I have inventory removed from current and put into sold, when the sold_date field is entered and saved.

I am using the "On Save" form event to cause the email to be sent. The condition I am using for the event is:

isnotblank("date_sale")

The event should fire and cause the email to be sent when the sold date in entered and saved.

This does not work and I don't understand why, any ideas what I am doing wrong?

[Tom Cone Jr]

Re: Form Event "On Save" Help

sold_date

or

date_sale

???

[twwtc]

Re: Form Event "On Save" Help

Sorry, both are date_sale

[Mike Wilson]

Re: Form Event "On Save" Help

It is not clear what.... "This does not work" ... might means to you, or what you want it to mean to us. How are you assureing a "fire" or a "missfire"?

If I add this to the form OnSave event, it fires the message appropriately when I add a date to the date_sale field and save the record.

if isnotblank("date_sale")
	msgbox("not blank")
end if

try adding the message to yours and see if it fires. If it does, it is not the isnotblank() code in that event that is your problem.

[twwtc]

Re: Form Event "On Save" Help

Thanks Mike
I will give this a try when back in the office on Friday.

When I say "it does not work" I mean that when I enter a date in the date_sale field and save the record, the event does not always fire.

I do experiment with the same few records to see if it works. I go into the sold records and delete the date_sale field so that the record is returned to current inventory and try the event again (by entering a date in the date_sale field. Could that have anything to do with it?

Thanks
Tony

[Mike Wilson]

Re: Form Event "On Save" Help

OK, Tony,
But what are you using as an indicator that the OnSave event fired or not? What is your signal that it has/has not fired? I recommend that you use something that is an absolute certainty for a signal like the msgbox() or ui_beep(). Using the outcome of a complex code like email code as the signal that the event has fired lends to misleading assumptions by the fact it might likely be the email code that is at fault and not the firing of the OnSave event.

[MikeC]

Re: Form Event "On Save" Help

Or even check the trace Window (Main Menu-->View-->Trace Window) and enable the Event tab so see the events that fire when doing something.....

[twwtc]

Re: Form Event "On Save" Help

OK, will try the trace window.

I assume the event does not fire when outlook express does not pop up with the attached report ready to send. There are times when outlook does appear with the attached report. Can't figure out why when a date is entered, outlook express does not always appear.

Maybe the trace window will give me some ideas.

Thanks
Tony

[Tom Cone Jr]

Re: Form Event "On Save" Help

While you're tracing, why not dump the contents of the date_sale field itself to the trace window to verify what Alpha is seeing.

In earlier versions of Alpha Five an empty date field would sometimes hold the slash marks, like this:

{  /  /    }

And, if memory serves, this would not be deemed a "blank" field. I think they've fixed this, but it's worth checking.

[twwtc]

Re: Form Event "On Save" Help

Tom & Mike

I decided to take the easy way out and put a button on the form to save the record and send the email. It is working great!

The only problem is getting a few salesman to hit the new button instead on the save button in the menu bar like they have done for years. You know old habits are hard to break.

Thanks for your help!!!