MIchaelFeldman1
Technical User
Hi,
I wrote a system in Powerbulder 6.0 a while back (mid 2000's) and it was working with MSSQL Server 2008 on a Windows Server 2008R2 up to now (and is still working). It was connecting via ODBC. The system logged into a DB via a DB user name, then that user name was looked up in custom tables and read permissions for the application (all permissions were defined in custom tables and have nothing to do with DB permissions). Again, these permissions are read by code.
I needed to move to a different server.
New Server:
Microsoft Server 2016R3
MSSql Server 2017
The same application logs into the old DB and is able to have the right custom (code defined) permissions.
However, when logging into the new DB (exactly replicated from the old) - the same application does not read the custom permissions for the user (though it does log into the DB successfully).
This is really puzzling. I dont have source code .
Any ideas?
Thank you,
Michael Feldman
I wrote a system in Powerbulder 6.0 a while back (mid 2000's) and it was working with MSSQL Server 2008 on a Windows Server 2008R2 up to now (and is still working). It was connecting via ODBC. The system logged into a DB via a DB user name, then that user name was looked up in custom tables and read permissions for the application (all permissions were defined in custom tables and have nothing to do with DB permissions). Again, these permissions are read by code.
I needed to move to a different server.
New Server:
Microsoft Server 2016R3
MSSql Server 2017
The same application logs into the old DB and is able to have the right custom (code defined) permissions.
However, when logging into the new DB (exactly replicated from the old) - the same application does not read the custom permissions for the user (though it does log into the DB successfully).
This is really puzzling. I dont have source code .
Any ideas?
Thank you,
Michael Feldman