Re: [GENERAL] Bad locking with MS-Access

2005-07-25 Thread Zlatko Matic
realise problems with MS Access front-end. What problems could I expect ? Thanks, Zlatko - Original Message - From: Andreas [EMAIL PROTECTED] To: Ets ROLLAND [EMAIL PROTECTED] Cc: pgsql-general@postgresql.org Sent: Sunday, July 24, 2005 11:01 PM Subject: Re: [GENERAL] Bad locking

Re: [GENERAL] Bad locking with MS-Access

2005-07-25 Thread Andreas
Hi Zlatko, You mentioned: Use serial or serial4 to create auto-values. Don't use any bigint-types like bigserial. Access doesn't like 8-byte-ints.. Could you please explain why you don't recommend bigserial for primary key ? I use bigserial primary keys in Postgres tables, and din't

Re: [GENERAL] Bad locking with MS-Access

2005-07-24 Thread Andreas
Ets ROLLAND schrieb: For all the data created BEFORE the transfert to PostgreSQL, all works fine. For the records created SINCE this transfert, it is impossible to modify or delete these records !? MS-Access say that The record is acceded by an other user, even I am the only user. As

[GENERAL] Bad locking with MS-Access

2005-07-22 Thread Ets ROLLAND
Hello ! I made the port of an Access 2002Database to PostgreSQL 8, it seems to work. I still use MS-Access 2002 for the application, using ODBCwith linked tables. For all the data created BEFORE the transfert to PostgreSQL, all works fine. For the records created SINCE this transfert, it

Re: [GENERAL] Bad locking with MS-Access

2005-07-22 Thread Richard Huxton
Ets ROLLAND wrote: Hello ! I made the port of an Access 2002 Database to PostgreSQL 8, it seems to work. I still use MS-Access 2002 for the application, using ODBC with linked tables. For all the data created BEFORE the transfert to PostgreSQL, all works fine. For the records created SINCE