The original TRID go live date is upon us, part of me is sad it didn’t go, August 1st is my Dad’s birthday. October 3rd is the first Saturday in October, not far off. Were you ready on August 1st?
Over the next 2 months look at every document, every report for anything that is based on a HUD line. It will need updated.
During an installation of Softpro Classic SQL it is possible to run into a SQL database check error that won’t let you continue.The Error is Unable to establish a connection to the SQL Server
SoftPro Live has been around for a bit of time now. Early last year I did some research to determine who I could find that was running an active SoftPro Live site, I located 37 unique sites running on the Custom platform. This is not a complete list, it is possible to hide this service from search engines, and there’s no reasonable method to find people not on the customized platform, so this list is just taking a temperature. I wondered what that would look like 16 months later. (more…)
In Version 15 HF2 of SoftPro Classic, Pro1099 on some systems likes to start up needing local machine Administrator access. Not all machines, but some of them. I have clients who for good reasons don’t want users to have Administrator access. That usually happens as more hands touch more desktops.
There was a change in functionality from Standard 12.2 to Classic 15 HF3 where the DS Fields for most 800 and 1300 section fields no longer fill out the Lender’s name in the associated To: field. Enterprise 6.3 also works this way, so it’s likely a design feature. To a converted Standard user it appears to be an issue. A possible workaround is to put a single entry lookup table on the DS fields so that the user could quickly enter the information. The first interesting obstacle was pressing F9 in a drop down list results in no response from ProForm. Why would they expect someone to need a lookup table on a short drop down list. That seemed to be a show stopper, but then
A client recently upgrading from Standard 12.2 to Classic 15 HF3 had some single sided transfers that needed cleaned up in ProTrust. They were in pretty good shape with 110 of them in a 10 year database. As they were cleaning up the error message Unable to match the selected transactions. Ledger locking failed started appearing.
It started in late March, today the brakes are applied, we are now in a delay. The August 1st deadline for the TRID regulations has been delayed until October 1st. The party line is there was an administrative mistake that was just discovered, in the nick of time. I’m glad that thing showed up. That provides a little relief, not much, sometimes.2 months is a day in development. Here’s what they said,
