23.04.2008, 23:06 | #1 |
Участник
|
gatesasbait: Table caching and record delete()/update()/next
Источник: http://gatesasbait.spaces.live.com/B...B9F5!209.entry
============== Good morning, This is a very basic concept. If you get the following error: "Cannot call NEXT, update(), or delete() on buffer where data is selected or inserted in another transactionscope." It means that the record selected has table caching activated, such as 'NotInTTS' and that you attempted to, for example run code like the following: //wrong select firstonly forupdate aRecord; ttsbegin; aRecord.delete(); ttscommit; It is important in general and necessary for cached tables to begin the transaction scope before selecting the record for update. And so, even for tables that do not have caching enabled, it is strongly discouraged to call NEXT, update(), or delete() on a buffer outside of the transaction scope it was selected in. //good ttsbegin; select firstonly forupdate aRecord; aRecord.delete(); ttscommit; Источник: http://gatesasbait.spaces.live.com/B...B9F5!209.entry
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору. |
|
|
Похожие темы | ||||
Тема | Ответов | |||
axStart: Table caching in AX | 3 | |||
Говорят вышел SP2 для Axapta 3. Кто нибуть что знает на эту тему? | 10 |
Опции темы | Поиск в этой теме |
Опции просмотра | |
|