Today a client asked if we could add $7.00 to the first page of all Mortgage Recording fees in the state of California. There are 58 counties in California, some of them have multiple entries for varying costs.
Doing this sort of update manually is a huge pain. There are a number of different ways to mass update data in the lookup tables. I'm not a fan of using ODBC connections in Excel or Access to update lookup tables, there are slight differences in data formats which can cause information to disappear during the update. So it's SQL Server Management Studio to the rescue.
The only catch with using SQLSMS to do the update is the data is stored as a nvarchar() format, which is all good, but viewed as a string rather than a decimal. So a conversion of the data in the column needs to take place during the update.
In this client's case (and many others) the column that needs updated is called "Mortgage_Cost". ProForm uses a translation table to connect Fields to database columns. To find the correct column name first it's necessary to find the field name that needs updated. In this case it's MTRTE1 visible on the 1200 formula screen. Next bring up the lookup table and Modify Table, to show the Create/Edit Lookup Table screen
Find the field in question and notate the the value to the right of the equal sign, that is the column header in the table. The Table name itself is listed at the bottom of the screen.
For this update, the table name is County, and the Column name is Mortgage_Cost. let's make the SQL statement that will update the table.
Click the Execute button and the table will be updated. Now I highly recommend doing this on a test table before doing it on your live data, make sure you know precisely what the command is going to do prior to going live.
Notice that even though we are adding an even $7, there are 2 decimal places used. ProForm likes to see 2 decimal places and by using "7.00" rather than "7" we maintain those 2 places.
If you fail to use the Cast as Decimal SQL will concatenate the strings together putting something like "40.007.00" in the field, which of course will not evaluate in ProForm properly.