There are things that need checked after converting a database from Access to SQL with SoftPro Standard.  I've been through a couple of these, there are things to watch out for. Once the data is converted and with each database showing no unfixed issued during the conversion process, there are some additional items that need done, or checked.

 

First the File Numbering Manager is may be reset to the default of something like yySSSSS, Change that in SPAdmin under Preferences, to your previous file numbering format.

 

The other things under Preferences are normally set correctly but they are worth mentioning. First verify the Directories are set correctly.

If you don't know what they should be set to, here's what I know.  A default installation will have everything except Data Files Directory set to your SoftPro Shared Folder. If you have a consistent mapped path as the example shows, use that mapped path.  Otherwise you'll be entering a UNC Path, something like \\SBS2011\SoftPro\ works fine. Many times this is a UNC path, which I highly recommend not using for Data Files Directory.

 

Make sure the Default Template and GFE Template are properly set.

Verify the other options are as you expect them to me.  The sample is how I expect it.

Next Click on Global Preferences

If Default to GFE Files in 2010 Should be selected, be sure it is.  This was the second thing that was missed during the most recent conversion.  If you use ProScheduler check that setup screen, my clients tend to use ProCal an automatic calendaring system for ProForm which we built. It's pretty cool, it even has merge to email.

This next item won't apply if you don't run Pro1099.  If you do, there is some information that needs updated in Pro1099.

Start Pro1099 and navigate to the Tools -> Preferences window. If it's blank like this example, fill it out, then we need to update a database field.

 

Start Microsoft SQL Server Manager

Navigate to your SoftPro instance, or the default instance, then to the Pro1099 table and finally the P1WinSetup Table

Select Edit Top nnnn Rows,

Notate the column HighLockFile, if it's 00000001 it needs updated.

To determine the proper value Click on New Query

 

Put this in the Query Window

Use Pro1099
Select LockFile from P1Win order  by P1Win.lockfile Desc

  Click Execute

And the Query results will show the lock file column with the highest one at the top.

That is the value that we need in this case it is 000002PR.  So right click on that and select Copy

 

Now we have the value we need in the Copy Paste buffer.  Select the P1WinSetup Table and paste the value in the HighLockFile column's only row, or most current row as described by the VersionDate Column.

 

Usually there is only one row.

 

An issue here will show itself as a Pro1099 Error (P1WIN-042) Violation of Primary Key constraint 'Pk_P1Win". Could not insert duplicate key in object 'dob.P1Win'. TheSelec duplicate key value is (00000001)

Update the HighLockFile column to fix. 

ProTrust also has a HighLockFile and may experience the same sort of error message.

Run the following SQL Command

Use ProTrust
Select lockfile from PtWin order by PTWin.lockfile Desc

To find the high lock file.

Click Execute as above to see the Results.

Place the highest High Lock from the  query in  PtWinSetup's HighLockFile column of the most current row. This one wasn't on today's table of issues, I've seen it before and wanted to mention it.

So those are some of the issues that we've run across when updating ProForm Standard 12.2 from using Microsoft Access data tables, to using Microsoft SQL data tables.  We're not using ProIndex, I expect the same sort of issue HighLockFile to exist there also.  One of the beautiful things about ProForm is the consistency of the product.  Select, Enterprise, Standard all follow a consistent pattern, clearly Select has it's own pattern, and is more consistent, but they all duplicate thoughts well across themselves.