[AccessD] Trigger a macro

I think that is a very bad idea.  Either a field is required or not in
the table.  If it won't always be filled in, then it shouldn't be
required.  You can control entry with the BeforeUpdate event of a form
quite easily and it doesn't take any monkeying around with the back end.
That is the only practical way to handle values that are required under
some circumstances and not under others.

If the data entry is being done through a query or a table, STOP IT!
Forms are there for a reason:  they allow you to control things like
this and to keep the user from shooting themselves (and you) in the
foot! 


Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Johncliviger at aol.com
Sent: Saturday, April 01, 2006 2:21 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Trigger a macro

 
In a message dated 31/03/2006 17:39:16 GMT Daylight Time,
cfoust at infostatsystems.com writes:

Charlotte


Hi Charlotte
I'm changing the Required property in TableDefs and the vb code to do
that works fine in the backend but not in the frontend.
 
It could be that changing the Required property is not the best way
forcing data entry to a control. I have some records that require a
comment while others do not. If you see what I mean. So I was trying to
switch the Required property on and off as needed.
 
john cliviger
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com