[AccessD] A2K: Can't update (ADO) Recordset

A little brain fart myself.

The last one should be:
AdLockReadOnly = 4

On 3 Feb 2004 at 22:20, DWUTKA at marlow.com wrote:

> Thanks for catching that Stuart!  Massive brain fart!
> 
> Drew
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Stuart
> McLachlan
> Sent: Tuesday, February 03, 2004 9:24 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] A2K: Can't update (ADO) Recordset
> 
> 
> On 4 Feb 2004 at 13:44, Darren DICK wrote:
> 
> > Sigh
> > Still don't work
> > Now I get runtime error 3001
> > Arguments are of the wrong Type, are out of acceptable range,
> > or are in conflict with one another.
> > The the debug highlights the line...
> > 
> > rs.Open sel_SQL, con, 1, 512 
> > 
> > The field in the underlying table does exist. And is named correctly
> > I dunno
> > 
> 
> 512 is *way* out of acceptable range
> 
> ADBOB locktype constants are:
> adLockBatchOptistic = 1
> adLockOptimistic = 3 (the one you want)
> adLockPessimistic = 2
> AdLockReadOnly = 1
> 
>  
> -- 
> Lexacorp Ltd
> http://www.lexacorp.com.pg
> Information Technology Consultancy, Software Development,System 
> Support.
> 
> 
> 
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com

 
-- 
Lexacorp Ltd
http://www.lexacorp.com.pg
Information Technology Consultancy, Software Development,System Support.