JnlLineDim.LOCKTABLE(TRUE, FALSE); Raises an Error

Toddy_Boy
Member Posts: 232
Hi Guys
Can anyone explain why this code would raise the locked by another user error in the form of a message box with an OK button as opposed to the standard message box which informs of the lock then closes automatically when the lock is released (as happens previously in the executed code)? ](*,)
Client 3.70.B DB 2.01.B Native
Can anyone explain why this code would raise the locked by another user error in the form of a message box with an OK button as opposed to the standard message box which informs of the lock then closes automatically when the lock is released (as happens previously in the executed code)? ](*,)
Client 3.70.B DB 2.01.B Native
Life is for enjoying ... if you find yourself frowning you're doing something wrong
0
Comments
-
1) are you sure it is a LOCKTABLE(TRUE,...) and not a LOCKTABLE(FALSE,...)?
2) if not 1) then, are you sure there is no LOCKTABLE(TRUE,...) before current one in the same transaction? (I am not completely sure that the first LOCKTABLE will be kept or if the second will be used)
In these cases it is normal behaviour.Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0 -
Hi Kriki
Thanks for the quick reply, I am definitely sure it's LOCKTABLE(TRUE, the puzzling thing is the error message with the OK button and not a message that's shown and disappears?
I don't think this table is locked previously within this transaction however other tables are locked.Life is for enjoying ... if you find yourself frowning you're doing something wrong0 -
The fact that it is an error lets me think it is a LOCKTABLE(FALSE,...) because this means that if the table is locked, don't wait but generate an error.Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0 -
It's definitely LOCKTABLE(TRUE, FALSE) however the routine that locks the table is called a number of times. Could this be causing the error box to appear?Life is for enjoying ... if you find yourself frowning you're doing something wrong0
-
I think so yes. Probably it is already in a transaction when the routine is called.Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions