Thread: Question

Question

From
"David \(Wojo\) Wojciechowski"
Date:
when using a vb recordset static and pessimistic lock type.


why is it when I try to update or delete a record from the recordset i get a
message that the records could not be located for update or delete.

I also get this in pgadmin alot too.

but i don't get it all the time.

Please help i have a really big head ake over this......

I'm Wojo

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Revolutionary:  Disk drives go round and round.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Dave (Wojo) Wojciechowski
MFI Technical Support Specialist

Help Desk (330) 759-3006 Option # 8
Help Desk E-Mail:  support@morgansfoods.com

PERSONAL WORK VOICE:  (330) 759-3006 Ext. 122
OFFICE FAX:  (330) 759-7231



Re: Question

From
"Ryan C. Bonham"
Date:
Davin,

Can you turn on CommLog in the ODBC Driver run your VB Code and then send me
the log.
Also what version of the ODBC Driver are you using? Try 7.01.0008 if you are
using an earlier version.

Ryan

> -----Original Message-----
> From: David (Wojo) Wojciechowski
> [mailto:david.wojciechowski@morgansfoods.com]
> Sent: Sunday, October 28, 2001 4:27 PM
> To: pgsql-odbc@postgresql.org
> Subject: [ODBC] Question
>
>
> when using a vb recordset static and pessimistic lock type.
>
>
> why is it when I try to update or delete a record from the
> recordset i get a
> message that the records could not be located for update or delete.
>
> I also get this in pgadmin alot too.
>
> but i don't get it all the time.
>
> Please help i have a really big head ake over this......
>
> I'm Wojo
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Revolutionary:  Disk drives go round and round.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Dave (Wojo) Wojciechowski
> MFI Technical Support Specialist
>
> Help Desk (330) 759-3006 Option # 8
> Help Desk E-Mail:  support@morgansfoods.com
>
> PERSONAL WORK VOICE:  (330) 759-3006 Ext. 122
> OFFICE FAX:  (330) 759-7231
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>