Hi Guys,
We got a strange situation where we need to create/modify text for closed sales order, which is not allowed in DAL thru standard session (tdsls4500m000). Therefore we decided to have simple display session (customized) to maintain text for selected record.

Now the problem is, since the new custom session is based on tdsls400 (main table), it is going thru DAL for any updates and it is not letting to modify the text based on some DAL conditions.

Is there any way I can disable DAL for this table in this custom session? I dont know what to do?

I appreciate your help

regards

Use the db.insert or db.update

or

skip the execution of property checks by making the property flag false. See the programmers' manual: http://www.baanboard.com/programmers_manual_baanerp_help_functions_db_operations_dal_update

Hi Kees,
Thanks for your response.
The problem here is we have not written any code in the program script. It is simple session created used Generate Session. The program script doesnt have any code. It is simple display session and we just enabled Text Manager in standard commands at form level to allow user to enter some text. I dont know where I can use db.update().

regards

Ravi,

In the choice section of the UI-script, the "choice.text.manager:" an be used.

Kees,

Lets put forth a hypothetical table with a dal with the following condition:function extern long before.save.object()
{
if somecondition then
donotallowanyupdates
endif
}
Now even if Ravi is creating a new session based on this table, he will not be able to update the text if "somecondition" becomes true. I understand in an update session one has the luxury of using db vs. dal statements to make the determination but how about a maintain session.

Guys,
I got the solution with text.edit(). To bypass standard text manager, I added two commands to specific menu. Now I am able to edit text without going thru standard DAL.

Thought I could share!

regards

Hi friends,

We also got similar issue, we were trying to add text to a standard Session through a customized table.

We got the error as below:
Errno 0 bdb_errno 205 (Out of range)
Log_mesg: Error 205 (Out of range) on tcibd420395 in db_update(51)

We tried many options but couldn't solve it.
Finally after calling text.edit() and skipping the standard choice.text.manager: section using choice.again()
We are able to successfully add the text without errors/issues.

sample code:
choice.text.manager:
before.choice:
handle.text.manager()
choice.again()

function void handle.text.manager()
|* Customized function for handling text.
{
whtyc001.text = 0
db.retry.point()
select whtyc001.*
from whtyc001 for update
where whtyc001._index1 = {:whinp100.koor,:whinp100 .orno, :whinp100.kotr,:whinp100.pono,
:whinp100.ponb,:whinp100.boml,:whinp100.effn}
selectdo
text.edit("whtyc001.text",language$,"","","","","","",3)
db.update(twhtyc001, db.retry)
selectempty
whtyc001.koor = whinp100.koor
whtyc001.orno = whinp100.orno
whtyc001.kotr = whinp100.kotr
whtyc001.pono = whinp100.pono
whtyc001.ponb = whinp100.ponb
whtyc001.boml = whinp100.boml
whtyc001.effn = whinp100.effn
text.edit("whtyc001.text",language$,"","","","","","",3)
db.insert(twhtyc001, db.retry)
endselect
commit.transaction()
}

Thought to share!

thanks,
Satish

Hi Guys,
We got a strange situation where we need to create/modify text for closed sales order, which is not allowed in DAL thru standard session (tdsls4500m000). Therefore we decided to have simple display session (customized) to maintain text for selected record.

Now the problem is, since the new custom session is based on tdsls400 (main table), it is going thru DAL for any updates and it is not letting to modify the text based on some DAL conditions.

Is there any way I can disable DAL for this table in this custom session? I dont know what to do?

I appreciate your help

regards

hi,

if you know text number, to modify the text you can go through session tttxt1100m000 and try if it allows.

regards,
Vishal

Came across this thread while having a similar issue:

I have a new session displaying some fields of sales order line (order nr, pos, bp) and statistic group. The idea is that the stat. group is editable, the user can change its value for each line at each time; ALSO when according to DAL no changes are allowed (delivered, invoiced, etc).

The neatest way to achieve this would be to write an after.rewrite section on the main.table.io in which all records of tdsls401 & tdsls451 are updated accordingly. The only thing needed is then to bypass the DAL, for otherwise you cannot perform the changes.

Any ideas?