Users of Microsoft Dynamics NAV 5.0 Grapple with Approaches to Handling "Table Locking"
PUBLISHED: August 8, 2008
Oftentimes, a problem shared among various organizations reflects a larger unmet need across a particular user group. In a NAV User Group webinar last month, "Go Live," recent adopters of Microsoft Dynamics NAV 5.0 voiced their concerns about "table locking" in NAV. Ultimately, the issue revealed the invaluable role of experienced programmers and value added resellers (VARs) in order to correctly and effectively maximize Nav 5.0.
A user in the manufacturing industry who recently adopted NAV 5.0 (running on SQL version 4), explained that his company's product orders, which come in via its website, are programmed to import directly into NAV. However, at times the program inconveniently locks when information is being manually entered into tables that are simultaneously being accessed by the import function in NAV.
Terry Murphy, a Microsoft Dynamics NAV Partner, offered a temporary fix to minimize this problem. Organizations undergoing a significant amount of ongoing transactions should schedule automated tasks during office downtime (e.g. after midnight) to avoid collision with manual processes.
A user in the manufacturing industry who recently adopted NAV 5.0 (running on SQL version 4), explained that his company's product orders, which come in via its website, are programmed to import directly into NAV. However, at times the program inconveniently locks when information is being manually entered into tables that are simultaneously being accessed by the import function in NAV.
Terry Murphy, a Microsoft Dynamics NAV Partner, offered a temporary fix to minimize this problem. Organizations undergoing a significant amount of ongoing transactions should schedule automated tasks during office downtime (e.g. after midnight) to avoid collision with manual processes.
Log in or activate your FREE membership for full article access.
