Skip site navigation (1) Skip section navigation (2)

Re: MSysConf on PG 8.2 ?

From: greg(dot)campbell(at)us(dot)michelin(dot)com
To: "Frank Brown" <frankjbrown(at)gmail(dot)com>,pgsql-odbc(at)postgresql(dot)org
Subject: Re: MSysConf on PG 8.2 ?
Date: 2007-03-05 22:36:37
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
I always strive for simplicity. 
If I were going to set up a MSysConf table, my first thought would be to 
use pgAdmin III to create one in schema public.

Since I haven't  done this, I cannot say  whether it will work or not.
Access wants to attach SchemaName_ to table names, such as 
"public_MSysCont", but this just is just an alias that can be altered by a 
rename directly, on in MSysObjects table of Access (must have option to 
view system objects turned on)

Greg Campbell ENG-ASE/Michelin US5-US7
Lexington, South Carolina
803-951-5561, x75561
Fax: 803-951-5531

"Frank Brown" <frankjbrown(at)gmail(dot)com> 
03/04/2007 21:10

"greg(dot)campbell(at)us(dot)michelin(dot)com" <greg(dot)campbell(at)us(dot)michelin(dot)com>

Re: [ODBC] MSysConf on PG 8.2 ?

Greg...   My database contains several schema' within the database.   Some 
of these are 'System Objects' such as Infromation Schema, others are are 
for different but related modules of the application.    I would have to 
think that this table should be built under a 'System Object' but where? 

On 3/3/07, greg(dot)campbell(at)us(dot)michelin(dot)com <greg(dot)campbell(at)us(dot)michelin(dot)com > 

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

"Frank Brown" <frankjbrown(at)gmail(dot)com> 
Sent by: pgsql-odbc-owner(at)postgresql(dot)org 
03/02/2007 19:55 


[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! 

pgsql-odbc by date

Next:From: noreplyDate: 2007-03-06 11:33:06
Subject: [ psqlodbc-Bugs-1002454 ] ODBC-Driver uses false Selectstatement.
Previous:From: Karl DenningerDate: 2007-03-05 15:31:02
Subject: Re: ODBC problem with Microsoft Word and Excel

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group