Since we upgraded from Pervasive database to SQL in Estimating 20.1, when users open an existing estimate, the estimate opens up in the incorrect database. Users have to manually change the database accordingly and then proceed to work on the estimate. This is very frustrating as there are thousands of estimates that were migrated to SQL Estimating.
by: Lou P. | over a year ago | Other
Comments
This is an issue with the importing of estimates to SQL Estimates and is required to assessed ASAP as this is impacting the business