A customer is running a customization which has a third party table (Extending the SOP Line Details) associated to it. The table is managed by the dexterity customization and has been confirmed to exist in both the Production and Test Copy of the Production Company Database.
THE PROBLEM:
The client is having save operation errors when trying to access the third party table from within a test company when the user does not have user access to the production company database?
We have checked all the usual things like user access, alternate forms security access, security tasks, sql database DynGrp role permissions and user security.
What we have determined.
Client maintains 1 Production Company Database, 1 Test Company Database based on the the Production Company Database, and TWO (Fabrikam).
The customization works fine in the Production Company Database and Fabrikam.
And will work in the Test Company Database, so long as the "user access" is enabled for the Production Company Database.
"But the user is logged into the Test Company Database?"
However, if the user access if turned off for the Production Company Database, the user can no longer save to the customization table within the Test Company Database. Further, I do observe that the data from the third party table is retrieved correctly to the GP alternate window, the error occurs when I change a record in the third party table and attempt to save.
I have never seen this before where user access to one company would affect the operation in another company and hope that someone can shed some light on why this would occur?
I am thinking it may be the test company database, a copy of the production database, could be the problem.
And it has been confirmed that the security tsql scripts were run after restoring the production to the test database and grant was executed as well.
Any help would be appreciated, as I say, been developing for years and have never seen this.
Michael Smith
DTM Systems Corp.
