<div>
No error is generated to be caught in &quot;On Error&quot;.<br />
<br />
As far as the return value on an execute, does anyone know how to do that in ADO?<br />
<br />

</div>


No error is generated to be caught in "On Error".

As far as the return value on an execute, does anyone know how to do that in ADO?



<div>
I hate to bother you again, but I don't see how this works in ADO. &nbsp;I don't see that &quot;.execute&quot; has a return value. &nbsp;What am I missing?
</div>


I hate to bother you again, but I don't see how this works in ADO.  I don't see that ".execute" has a return value.  What am I missing?

<div>
<div class="content wysiwyg-content">
Experts,<br />
<br />
I just set up a relationship in Access between two tables that enforces one-to-many referential integrity. &nbsp;When I tried to delete the parent record from the query window, I was warned that I would leave orphans in the child table, as I should be.<br />
<br />
When I run the same query from my VB code, it doesn't delete the parent record (which is good), but it never throws any kind of error telling me I'm about to screw up the database. &nbsp;Is there any way I can have the VB program let me know when a potential violation of referential integrity is about to take place?
</div>
</div>


Experts,

I just set up a relationship in Access between two tables that enforces one-to-many referential integrity.  When I tried to delete the parent record from the query window, I was warned that I would leave orphans in the child table, as I should be.

When I run the same query from my VB code, it doesn't delete the parent record (which is good), but it never throws any kind of error telling me I'm about to screw up the database.  Is there any way I can have the VB program let me know when a potential violation of referential integrity is about to take place?

VB/Access Referential Integrity

Visual Basic is Microsoft’s event-driven programming language and integrated development environment (IDE) for its Component Object Model (COM) programming model. It is relatively easy to learn and use because of its graphical development features and BASIC heritage. It has been replaced with VB.NET, and is very similar to VBA (Visual Basic for Applications), the programming language for the Microsoft Office product line.