I am having a strange issue with cascading deletes in that it simply isn't
cascading. Heres what I'm using:

VB .NET 2005 sp1
SQL Express 2005

For simplicity, I will give 2 of the many table adapters in the app and
their relations:

Sites
-----
(PK) Name
ContractType
ContractExperation
Address1
Address2
City
State
Zip
Phone
Fax
VPNType
VPNName
VPNUser
VPNPass
VPNNotes
VPNHostOrIP
VPNUserConfigFile
VPNFileName
VPNFile
Office
--------------

Servers
--------
(FK)Site
(PK)Name
ServerRole
IPAddress
NetworkType
ProtocolType
DNS
WINS
Gateway
LocalUser
LocalPass
Location
--------------

Relationship
------------
(P)Sites:Name<----------(C)Servers:Site
Both Relational and Foreign Key Constraint
Update Rule:Cascade
Delete Rule:Cascade
Accept/Reject Rule:Cascade

I use an SQL command as part of the DataTable in the designer called
FilLByOffice to load the dataset for a given office name for the Sites
DataTable.
These results are populated into a TreeView

I use an SQL command called FillBySite to populate the Servers DataTable for
the given Site.
These results are populated into a ListView

I am able to create records, and looking at the Database itself I see that
they records are being saved correctly.

However, when I run the SQL Command DeleteByName(@Name) from the Sites
DataTable (in code), the cascade does not work, leaving orphan records in
Servers. Thus, the next time the Servers DataTable is loaded, an error occurs
because there is not a parent record in Sites (the parent record was deleted
correctly).

I cleared all other relationships to rule out problems on that end
(ultimately I would like to have a few cascading deletes) and am still having
a problem. What could be causing this? Any help would be greatly appreciated,
I have not been able to find a similar problem by searching several forums
and knowledgebases.

strings vs regular expressions
OO Architecture Question
Append Nodes to existing XML File/Document .net 1.1
Net Framework 3 loads up 2 as well?
Master Volume Control in C#