[AccessD] update wouldn't run

I wonder if you dropped the key and then ran it if it would work. then
you could reset the key after. Multi-field keys might have different
rules. Doing one record at a time in a table view might have different
rules than a mass change in a query.

Hope you made a copy of the db or at least the table before you
touched anything though. Always want to have a way to return to the
before state, especially when you are working with other peoples
databases.

Stuff happens. ;-)

GK

On Tue, Jul 19, 2011 at 10:21 AM, Susan Harkins <ssharkins at gmail.com> wrote:
> When I used Datasheet view to see the uncommitted results, I saw only the
> original values.
>
> Susan H.
>
>
>> If you do that kind of thing in a QBE window, you can preview the results
>> before committing the results. I do that always. Still, it is a bit scary
>> when you push that action button and then look for unexpected issues.
>>
>>
>>
>>> I'll never forget the time a developer who worked for me decided to
>>> update
>>> all of a certain numeric string to a text number in an address field. The
>>> query ran and worked...sort of.  He had forgotten to provide for spaces
>>> around numeric string. I had to go through thousands of records and find
>>> every instance of "two" in a longer number and replace it with "2"!
>>>
>>> Charlotte Foust
>>>
>>> On Tue, Jul 19, 2011 at 3:46 AM, Susan Harkins <ssharkins at gmail.com>
>>> wrote:
>>>
>>>> No, they were both text -- I checked that and Access automatically knew
>>>> that the field was text and took care of it for me. I never call myself
>>>> an
>>>> expert. :)
>>>>
>>>> Susan H.
>>>>
>>>>>
>>>>> Your query may have tried to update a text 20 to a numeric 21, which
>>>>> would
>>>>> have been the wrong type and should not have worked.
>>>>>
>>>>> Just a guess ...
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>



-- 
Gary Kjos
garykjos at gmail.com