Upgrade Toolkit

4.2 LOCATING ILLEGAL LOCKTABLE CALLS
4.2 Locating Illegal Locktable Calls
You must identify and correct any illegal locktable calls that are made in the
customer’s database.
Note
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
You must only carry out this procedure if you are upgrading from Navision Financials
2.00 or 2.01.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To locate any illegal locktable calls that may exist in the customer’s database:
1 Open the new customized Navision database. Open the Object Designer and
export all the objects to a text file called objects.txt.
2 Locate the Findlock.exe file in the Upgtk folder on the product CD and copy it to
a suitable folder on your PC.
3 Open a command prompt. Set the folder you just copied the Findlock.exe file to
as the working folder and run:
findlock locks.txt
to find all occurrences of possibly illegal LOCKTABLE calls.
The locks.txt file that is generated will contain a list of all the LOCKTABLE calls
that might be illegal and the objects that contain these calls.
4 Open the locks.txt file and change the relevant code.
To ensure that the application can run on both Navision Database Server and SQL
Server, you must change some of the code. Similar code changes have already
been made to the base application in the new Navision that the customer is going to
use from now on.
You must check the code to ensure that every LOCKTABLE call listed in the file
(where the object containing the call has been customized, and where the first
argument is FALSE or the second argument is TRUE) is not made when the
application is running on SQL Server. Such calls are not supported on SQL Server.
In addition, if the second argument for LOCKTABLE is TRUE, you are implementing an
optimistic locking scheme. You cannot do this when you are using the SQL Server
Option for Navision. You must lock the records before you read them.
39