MSysConf on PG 8.2 ?

MSysConf on PG 8.2 ?

am 03.03.2007 01:55:32 von Frank Brown

------=_Part_22851_19984488.1172883332599
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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!

------=_Part_22851_19984488.1172883332599
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Greetings all... 
We have a PG 8.2 database upon which we report u=
sing MS Access using 8.02.02 psqlodbc35w.dll dated 10/24/2006.   =
I've noticed errors being returned within the logs such as " relat=
ion 'msysconf' does not exist"  .   There are a=
lso errors regarding authentication for user "Admin" failing.&nbs=
p;   Our Access front end seems to work fine, but we would like t=
o make sure everything is proper and as efficient as possible.   There=
is no user Admin defined,   do I need one?   &nbs=
p; 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 configur=
ation 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?  &n=
bsp;     Thanks!=20



------=_Part_22851_19984488.1172883332599--

Re: MSysConf on PG 8.2 ?

am 03.03.2007 02:12:14 von Richard Broersma Jr

> 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" .

I am getting this error in my postgresql log files also.

this is what I am seeing in various places in my pg_log file:

2007-03-01 13:44:39 LOG: statement: select oid, typbasetype from pg_type=
where typname =3D 'lo'
2007-03-01 13:44:40 LOG: statement: SELECT Config, nValue FROM MSysConf
2007-03-01 13:44:40 ERROR: relation "msysconf" does not exist
2007-03-01 13:44:40 STATEMENT: SELECT Config, nValue FROM MSysConf

Regards,
Richard Broersma Jr.


---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate

Re: MSysConf on PG 8.2 ?

am 03.03.2007 02:27:42 von Joshua Drake

Richard Broersma Jr wrote:
>> 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" .
>
> I am getting this error in my postgresql log files also.
>
> this is what I am seeing in various places in my pg_log file:
>
> 2007-03-01 13:44:39 LOG: statement: select oid, typbasetype from pg_type where typname = 'lo'
> 2007-03-01 13:44:40 LOG: statement: SELECT Config, nValue FROM MSysConf
> 2007-03-01 13:44:40 ERROR: relation "msysconf" does not exist
> 2007-03-01 13:44:40 STATEMENT: SELECT Config, nValue FROM MSysConf
>

I don't use the lo type but it looks like you need to install it from
contrib.

Joshua D. Drake

> Regards,
> Richard Broersma Jr.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
> http://www.postgresql.org/about/donate
>


--

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/


---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate

Re: MSysConf on PG 8.2 ?

am 03.03.2007 02:37:18 von Richard Broersma Jr

=20
> I don't use the lo type but it looks like you need to install it from
> contrib.

Uptil now, I didn't think that I did either. :-) =20
I will install it to see what happens.

Regards,
Richard Broersma Jr.


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Re: MSysConf on PG 8.2 ?

am 04.03.2007 01:42:04 von Greg Campbell

This is a multipart message in MIME format.
--=_alternative 0003BDC585257294_=
Content-Type: text/plain; charset="US-ASCII"

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

http://msdn.microsoft.com/archive/default.asp?url=/archive/e n-us/dnaraccessdev/html/ODC_ServerApplicationDevelopment.asp


Greg Campbell ENG-ASE/Michelin US5-US7
Lexington, South Carolina
greg.campbell@us.michelin.com




"Frank Brown"
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!

--=_alternative 0003BDC585257294_=
Content-Type: text/html; charset="US-ASCII"



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




http://msdn.microsoft.com/archive/default.asp?url=/archive/e n-us/dnaraccessdev/html/ODC_ServerApplicationDevelopment.asp





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!



--=_alternative 0003BDC585257294_=--

Re: MSysConf on PG 8.2 ?

am 05.03.2007 23:36:37 von Greg Campbell

This is a multipart message in MIME format.
--=_alternative 007C16AC85257295_=
Content-Type: text/plain; charset="US-ASCII"

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
greg.campbell@us.michelin.com




"Frank Brown"
03/04/2007 21:10

To
"greg.campbell@us.michelin.com"
cc

Subject
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.campbell@us.michelin.com
wrote:

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

http://msdn.microsoft.com/archive/default.asp?url=/archive/e n-us/dnaraccessdev/html/ODC_ServerApplicationDevelopment.asp



Greg Campbell ENG-ASE/Michelin US5-US7
Lexington, South Carolina
greg.campbell@us.michelin.com



"Frank Brown"
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!


--=_alternative 007C16AC85257295_=
Content-Type: text/html; charset="US-ASCII"



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

greg.campbell@us.michelin.com










"Frank Brown"
<frankjbrown@gmail.com>

03/04/2007 21:10







To

"greg.campbell@us.michelin.com"
<greg.campbell@us.michelin.com>


cc



Subject

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.campbell@us.michelin.com
<greg.campbell@us.michelin.com
> wrote:



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"
<
>


Sent by:


03/02/2007 19:55









To




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!





--=_alternative 007C16AC85257295_=--