Understand OLE-DB security settings and remote connections
- Last UpdatedFeb 24, 2025
- 2 minute read
Security settings could inhibit network access to remote .mdb files when AVEVA Production Management uses the Jet provider to connect to a remote Access database. In this situation, you might receive a message that the file is already opened exclusively by another user, or you require permission to view its data. Jet access to local files does not exhibit this behavior.
If you cannot move the .mdb file to the computer that hosts Server, a workaround for this behavior is to run SQL Server or MSDE on the same computer as the .mdb file, create a linked server to it, then access the .mdb file through the linked server with the SQLOLEDB provider rather than the Jet provider.
When you connect to a remote SQL Server, leave the IntegratedSecurity property blank, do not select SSPI, and type the values of an authorized logon for the Username and Password properties. AVEVA™ Production Management ignores these values when you use SSPI.
You can use the Microsoft Data Link Properties dialog box to build a string version of this connection information, referred to as a connection string, which you can save and examine to determine the values necessary to properly configure your OLE DB connector properties. For more information, see About the OLE-DB connection string.