I think I also found one useful switch. In the ODBC-driver's setting there is
one "extra" or so field, where 4 possible values can be entered: 0x0, 0x1,
0x2... If I remember right with 0x2 the driver mimics an SQL-Server auto
increment, which Access acknowledges.
However, does anyone knows go
A comment on the MS access/PG problem.
We experienced this problem as well and I isolated the problem to access's
support of timestamp.
PG defaults to timestamp(6), While access only supports timestamp(2).
When access fills the grid from the table, the values are truncated to ts(2).
On Fri, May 21, 2010 at 1:15 AM, Craig Ringer
wrote:
> Really?
>
> I had problems with Access complaining that the object it just inserted had
> vanished, because the primary key Access had in memory (null) didn't match
> what was stored (the generated PK). I had to fetch the next value in the PK
On 21/05/2010 9:56 AM, Richard Broersma wrote:
On Thu, May 20, 2010 at 5:52 PM, wrote:
I'm new to triggers in PostgreSQL. I have to create a trigger on insert to
increment a sequence to overcome MS-Access' limitation in acknowledging
serial "datatype".
Uh? Access doesn't need to acknowledge
> On Thu, May 20, 2010 at 5:52 PM, wrote:
>
>> I'm new to triggers in PostgreSQL. I have to create a trigger on insert
>> to
>> increment a sequence to overcome MS-Access' limitation in acknowledging
>> serial "datatype".
>
> Uh? Access doesn't need to acknowledge the serial datatype.
> At-least
> On Thursday 20 May 2010 5:53:51 pm tla...@gwdg.de wrote:
>> I'm new to triggers in PostgreSQL. I have to create a trigger on insert
>> to
>> increment a sequence to overcome MS-Access' limitation in acknowledging
>> serial "datatype".
>>
>
> You know serial is just a shortcut for:
>
> pid int NOT
