Posted by Rico on 04/22/06 20:07

Yea, I know what you're saying (and that should have been UPDATE HOUSE). My
comment wasn't on the practicality of identifying records, but on the
updatability of the table (since the table is not updatable with no ID). In
a perfect world, there would be no bad design, but I have the uneviable task
of converting a poorly designed Access FE to use an SQL Server back end.
The table in question has a single record in it, and was never intended to
have anything more than a single record in it. There is no ID field, just a
field that is updated to either 'Yes' or 'No'. If I had the budget I would
rewrite the whole program, which is very intensly complicated in terms of
the information, calculations etc (it's forestry related), so it would be a
greater task to take this crappy design and rebuild it properly. FWIW I
always use an ID field, that's how I was taught. I would just like to know
if there is reasoning that the table is not updatable without an ID field.




"Greg D. Moore (Strider)" <mooregr_deleteth1s@greenms.com> wrote in message
news:zds2g.7701$sq5.4088@newsread2.news.atl.earthlink.net...
>
> "Rico" <me@you.com> wrote in message news:f2s2g.5832$Fd6.4310@edtnps82...
>> Just because I don't know the address, doesn't mean the people that own
>> it
>> can sell it (UPDATE People Set Owner=NewOwner).
>
> Congratulations, you've just updated every record in your table to the new
> owner.
>
> In other words, you've just sold every house on the block to the same
> person.
>
> You need a where clause and in order to pick a SPECIFIC house, you need
> something that ID's it uniquely.
>
>
>>
>> "Lyle Fairfield" <lylefairfield@aim.com> wrote in message
>> news:1145701034.778574.144660@e56g2000cwe.googlegroups.com...
>> > How would you find the house if you didn't know the address?
>> >
>>
>>
>
>

[Back to original message]