A
Andy
Hi, I've created a .net 2.0 web app that uses Sql Server 2005 express
as its backend. I used microsoft's database tool to create all of the
membership, roles, etc. need for my website. Everything is working fine
except when I try to delete a user using the
Membership.DeleteUser(username as String) function. The error I get is:
The DELETE statement conflicted with the REFERENCE constraint
"FK__aspnet_Me__UserI__173876EA". While I understand this is yelling at
me about a foreign key validation, I'm not sure what I'm doing wrong.
I've done all the default steps recommended by microsoft to create my
web app and the backend user database, meaning the foreign key was put
their by default. Is it possible to delete users using the DeleteUser
method of the Membership class? I'm pretty new to 2.0 and the
membership system, but since this is using the default settings for
everything, I'm not sure what I could do differently to avoid this
foreign key problem short of removing the foreign key, which would
introduce integrity problems. Thanks in advance, and if I should post
this in the sqlserver forum instead, let me know.
as its backend. I used microsoft's database tool to create all of the
membership, roles, etc. need for my website. Everything is working fine
except when I try to delete a user using the
Membership.DeleteUser(username as String) function. The error I get is:
The DELETE statement conflicted with the REFERENCE constraint
"FK__aspnet_Me__UserI__173876EA". While I understand this is yelling at
me about a foreign key validation, I'm not sure what I'm doing wrong.
I've done all the default steps recommended by microsoft to create my
web app and the backend user database, meaning the foreign key was put
their by default. Is it possible to delete users using the DeleteUser
method of the Membership class? I'm pretty new to 2.0 and the
membership system, but since this is using the default settings for
everything, I'm not sure what I could do differently to avoid this
foreign key problem short of removing the foreign key, which would
introduce integrity problems. Thanks in advance, and if I should post
this in the sqlserver forum instead, let me know.