Hi Martin

Yep, that is the method this line of code comes from. I failed to notice the comments.... Ooops.

For info
This is one of 18 databases that needed to be renamed - no don't ask why. The renaming process worked for all databases except this one. Parts of the third-party application also could not access the database, so thankfully not just a DataFlex issue.

The databases were renamed by
  • Doing a backup
  • Detaching the database
  • Moving the MDF & LDF files to a backup folder -just in case
  • Restoring the database under the new name - we need the MDF & LDF files to match the DB name - again no don't ask why
  • Manually edit the third-party application config record.


This was most confusing as
  • SSMS could logon and access the database
  • DataFlex Studio could logon to the database
  • DataFlex application could logon to the database
  • DatalFlex connection could NOT be redirected to the database
  • Third-party application could access the database
  • Third-party application reporting could NOT access the database


We solved the problem by
  • Creating a new company in the third-party application, checking that it worked correctly
  • Pointed the new company at the database with the problem, everything worked as expected
  • Deleted the original third-party application company (this does not delete the database)
  • Renamed the new third-party application company to the old company name


Conclusion -something went wrong with the restoring of the security permissions on this database - no idea what though...