[AccessD] Dirty property

[Steve Schapel]

Oh Gustav, I fear it is you who have failed to read mine, and not the other 
way around!  :-)

I most certainly did read what you wrote, and my reply was directly thereto.

It looks like you were trying to enter:
    Is Not Null Or [OtherField] Is Not Null
as a field-level validation rule, not a table-level validation rule.  This 
is different from my suggestion of:
    [SomeField] Is Not Null Or [AnotherField] Is Not Null
as a table-level validation rule.

Forgive me if I have misunderstood.

Regards
Steve

-----Original Message----- 
From: Gustav Brock
Sent: Friday, July 24, 2015 9:13 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Dirty property

Hi Susan

So neither you nor Steve read my mails. I'm so disappointed ...

<quote>
I checked with a validation rule of:

    Is Not Null Or [OtherField] Is Not Null

But Access barks that other columns than the current cannot be used in the 
SQL.
</quote>

/gustav


-----Oprindelig meddelelse-----
Fra: AccessD [mailto:accessd-bounces at databaseadvisors.com] På vegne af Susan 
Harkins
Sendt: 24. juli 2015 00:30
Til: Access Developers discussion and problem solving 
<accessd at databaseadvisors.com>
Emne: Re: [AccessD] Dirty property

Steve, that might be exactly what I need. I'll take a look. Thanks for 
mentioning it.

Susan H.

On Thu, Jul 23, 2015 at 5:09 PM, Steve Schapel < 
steve at datamanagementsolutions.biz> wrote:

> You can use a table level validation rule, and in fact this is the way
> I would do it.  Under Table Properties.
> [SomeField] Is Not Null Or [AnotherField] Is Not Null
>
> Regards
> Steve
>
>
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com