Undeliverable Message

To: ISMTP(at)SFRA0046@Servers[<pgsql-interfaces-digest(at)hub(dot)org>]
Cc:
Subject: pgsql-interfaces-digest V1 #251

Message not delivered to recipients below. Press F1 for help with VNM
error codes.

VNM3043: DE_VOLDER Fabrice(at)ATR_EXPL_LYON1@SFR_DO_CNTR_EST

VNM3043 -- MAILBOX IS FULL

The message cannot be delivered because the
recipient's mailbox contains the maximum number of
messages, as set by the system administrator. The
recipient must delete some messages before any
other messages can be delivered.
The maximum message limit for a user's mailbox is
10,000. The default message limit is 1000 messages.
Administrators can set message limits using the
Mailbox Settings function available in the
Manage User menu (MUSER).

When a user's mailbox reaches the limit, the
user must delete some of the messages before
the mailbox can accept any more incoming messages.

---------------------- Original Message Follows ----------------------

pgsql-interfaces-digest Tuesday, March 2 1999 Volume 01 : Number 251

Index:

postdrv ODBC driver problems

----------------------------------------------------------------------

Date: Tue, 02 Mar 1999 22:54:31 -0500
From: Ben Gunter <bgunter(at)alef(dot)gcsu(dot)edu>
Subject: postdrv ODBC driver problems

After version 0.95 of PgAccess was released (thanks so much for the
quick response!), I figured my problems with character case were
resolved. Unfortunately, I tried to use the ODBC driver with MS Excel
97, and encountered the same problem. Tables with mixed case field
names gave me errors, and tables with all lower case field names worked.

MS Query could see the table fine (named "Present") and reported the
names of the fields fine ("First Name" and "Last Name"), but it failed
when I actually executed the query. It said: func_get_detail: no such
attribute or function "lastname".

This looks like the same problem I was having with PgAccess. Am I
missing something?

I'm using version 6.40.0004 of the ODBC driver, and PostgreSQL 6.4.2.

I'm sorry I don't have the logs right now. I can't get to the machines
I use Windows on until tomorrow. It shouldn't be too difficult to
recreate the error if you want to look into it. Just try to access a
table that uses mixed case field names and/or spaces. If you still want
to see the logs, let me know; I'll try to send them tomorrow.

Thanks,
Ben

------------------------------

End of pgsql-interfaces-digest V1 #251
**************************************