Re: ISQL - Reports with ACE (saceprep, sacego) - lock problem

A way around the problem is - Try placing the SQL into a stored procedure, then add the "set lock mode... " in the appropriate position in the stored procedure. Change the ace report to select from the stored procedure and there you have it. HTH, Stephen C Manga Email: Stephen.Manga@dbgroup.co.nz Stephen@quanta.co.nz On Thu, 28 Oct 1999, David Kleppinger wrote: > Reinhard Habichtsberg wrote: > > > > Jonathan Stowe <gellyfish@gellyfish.com wrote: > > > Reinhard Habichtsberg <Reinhard.Habichtsberg@unilux.de> wrote: > > > > in SQL statements, esqlc programs, even in odbc connections > > > > I can use "set lock mode to wait ...". Thereby the program does > > > > not stop if a table is locked temporary. > > > > > > You cant do it in an ACE report - you can only have select > > > statement. > > > > That's poor. Not the answer :-) but the fact :-( . > > Isn't there any workaround? > > As I had replied off-list, you can set the environment variable SACEISOL > to the value "DIRTY READ" and get the desired effect for ACE. > >

Stephen Manga <steve@quack16.quanta.co.nz> > > A way around the problem is - > > Try placing the SQL into a stored procedure, then add the "set lock mode... " > in the appropriate position in the stored procedure. Change the ace report > to select from the stored procedure and there you have it. > > HTH, > Hi Stephen, thanks for the tip. But I don´t know how to select from a stored procedure. The execute statement in ACE is not implemented. Sorry, can you help? Reinhard