Event Procedure to lookup value in table and perform action based onvalue

[steve]

I have a table called dates that has only one row and one column with
one date value. I want to write an event procedure on the Open Event
of a form that looks the value in the dates table and, if the current
date is greater than the value in the table, the form would close.

I am not sure what code or commands to use since I'm not that familiar
with writing Event Procedures.

Any help would be appreciated.

Steve

 

[Keith Wilby]

I have a table called dates that has only one row and one column with
one date value. I want to write an event procedure on the Open Event
of a form that looks the value in the dates table and, if the current
date is greater than the value in the table, the form would close.

I am not sure what code or commands to use since I'm not that familiar
with writing Event Procedures.

Any help would be appreciated.

Steve

Date is a reserved word in Access so if you're using it as a field name I'd
recommend changing it to something like fldDate. Check out the DLookup
function in the help, that should do what you want in the form's Open event.

Keith.
www.keithwilby.co.uk

 

[Larry Daugherty]

Compare [DLookup() the value in that table and field] with Now().

HTH

 

[Jeff Boyce]

Steve

If you want to compare to the current date/time value, use the Now()
function Larry mentioned.

If you want to compare to only the current date portion, use the Date()
function.

Regards

Jeff Boyce
Microsoft Office/Access MVP

Compare [DLookup() the value in that table and field] with Now().

HTH
--
-Larry-
--

I have a table called dates that has only one row and one column with
one date value. I want to write an event procedure on the Open Event
of a form that looks the value in the dates table and, if the current
date is greater than the value in the table, the form would close.

I am not sure what code or commands to use since I'm not that familiar
with writing Event Procedures.

Any help would be appreciated.

Steve

 

[Dale_Fye via AccessMonster.com]

Personally, I think I'd do the check before I open the form.

I assume that some event is causing the form to be opened. If that is the
case, I'd do the test before I even open the form. And if the event that
opens the form is tied to a command button, I might go so far as to disable
or hide the button if your criteria would prevent the form from opening.

The reason I say this is that cancelling a form opening will generate an
error, which you must handle; but if you do your test before you try to open
the form, you don't have to handle the error.

Just my 2 cents.

Dale