[dba-SQLServer] Validation rules and SQL Server

Thanks for the guidance Arthur.  The SQL table had the field set to Not
Allow Nulls.  Once I had cleared this the Access Form validation fired.  It
seems that the SQL checking fires before the Access form control checking.


-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Arthur
Fuller
Sent: Tuesday, 15 April 2014 12:59 a.m.
To: Discussion concerning MS SQL Server
Subject: Re: [dba-SQLServer] Validation rules and SQL Server

David,

I haven't seen this, but my first guess would be to check whether there's a
default value either on the control or in the SQL column. Failing that,
maybe you could investigate further by adding a MsgBox call on the control's
AfterUpdate event, and see what the value actually is after you blank the
control.

Arthur


On Sun, Apr 13, 2014 at 6:08 PM, David Emerson <newsgrps at dalyn.co.nz> wrote:

> Listers,
>
> I have a 2010 database accdb file which uses DSNless connections to 
> get recordsets for form and control sources.  It have a control which 
> is linked to tinyint field in an SQL 2008 table.  I have a validation 
> rule in the control "Is Not Null" and a Validation Text.  However if I 
> clear out the value in the field the validation rule doesn't fire.
>
> I have previously used adp's with SQL back ends and have not had this 
> problem.  Has anyone come across this before?
>
>
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com