MsysConf is a Microsoft thing, specifically a JET thing. When using a server database as a backend, there is the option of creating a MSysConf on your server database, that Jet will automatically check for some authorization and chunking options. And the "Admin" authentication has to do with the TryJetAuth, which tries to connect to server database as username Admin (like it was a remote Access database) right off the bat. This connection attempt can be turned off with a registry setting.
Neither TryJetAuth=1 nor MSysConf is required. They are optional items that can save some time at initial connection, but it probably will not be noticeable. All the articles you find about these will be old. But if you want to find out more I might suggest going to
Greg Campbell ENG-ASE/Michelin US5-US7 Lexington, South Carolina greg.campbell@us.michelin.com
"Frank Brown" <frankjbrown@gmail.com> Sent by: pgsql-odbc-owner@postgresql.org
03/02/2007 19:55
To
pgsql-odbc@postgresql.org
cc
Subject
[ODBC] MSysConf on PG 8.2 ?
Greetings all... We have a PG 8.2 database upon which we report using MS Access using 8.02.02 psqlodbc35w.dll dated 10/24/2006. I've noticed errors being returned within the logs such as " relation 'msysconf' does not exist" . There are also errors regarding authentication for user "Admin" failing. Our Access front end seems to work fine, but we would like to make sure everything is proper and as efficient as possible. There is no user Admin defined, do I need one? I have read quite a lot about setting up MSysConf table with my database, most of the information seems to be of earlier versions of PG. I also noted that PGAdmin III does not allow for the configuration of this table. So, should we build this table? If so, exactly where does it need to be built? Is there someplace where this is documented for the current versions? Thanks!