OK, first thing you need to do is forget about logicals. On any other
DBMS you wouldn't have them. You'd have the table (physical) and a
number of indexes built over it. There would be no way to directly
reference any of the indexes, you'd simply reference the table
(physical). Granted, I'm ignoring views here, but that's ok.
Now, for the updates to work the way you're trying to use them (I
believe, I don't use data adapters) there needs to be a primary key
constraint, or unique index built over the table. That means there needs
to be an index (logical) built over the physical that is specified
unique. You don't need to reference that index, the system will do so on
its own, but it has to exist. Is there some logical that's marked
unique? Can you create one?
As for the coding techniques, I know there's some upfront work, but once
you get a decent DAL (data access layer) running your productivity will
go through the roof! If you don't have a copy of SQLServer Express get
one. It's often easier to play with SQLServer than it is to play w/the
i. Then you can take what you've learned and apply it to i. I'd also
look (listen actually) to a number of the great podcasts on .net. A good
place to start is a recent Scott Hanselman blogpost listing the great
.net podcasts, there a link to my list in the bulleted list on his post.
(
http://www.hanselman.com/blog/HanselmanListOfPodcastsForNETProgrammers.
aspx)
-Walden
midrange.com
