Hey ya'll,
I'm experiencing an odd type of behavior. Here is the setup I think
is relevent. Visual Studio 2008, targeting c# 3. I have used the
design time tools to create a typed dataset. The database itself is
hosted on a full and separate instance of SQL Server (not a local SQL
Express instance that many folks seem to use). I have a third party
application that populates this database, of interest to my problem is
an intersection table used to drive user security and group membership
in this application. My task is to write an custom interface for our
help desk personnel to be able to manage group membership. So I have
a tables Users, Groups, and an intersection table, usersgroups,
comprised of (Not my doing - vendors apps) long non key descriptors
{(AutoNumber) ID, username, groupname). Now besides the tragedy of
not using keys for this table everything is working correctly.
In my app I have a two datagridviews, using the designer I assigned
dgv1 to the users table, and dgv2 I assigned to the relationship,
fk_users_usergroups that I established during the creation of the
dataset (the designer didn't autodetect). The master detail aspect
works correctly - clicking on a parent record in dgv1 displays child
records in dgv2 with the sole exception that the relationship only
successfully matches based on case. I have configured the dataset
itself to be case insensitive - but this has not corrected the issue.
Does anyone have any advice on what I might try?
PS. I can query the database from query analyzer and from ent.
manager with out any case restrictions.
Thanks
Brian
