ODBC driver for windows - question regarding holdlock

[MrRalphMan]

Hi all,

 

I am using a DSN less connection created within an Access db via VBA.

This is accessing a Sybase database via an ODBC connection.

 

I have been told that I cannot run my queries this way anymore as the windows ODBC driver uses a holdlock on the table, so even for a read only operation it locks the table.

I've locked the table for up to 45 mins before.. Oops.

 

Anyone know how to stop this happening?

 

Many Thanks,

 

Paul.

[paul_y3k]

err get ris of both and replace with Oracle ???

 

Can you not do something to your sql session to only do row locking ?

[MrRalphMan]

Well the connection is set up for read only and I'm not sure what to look for in the ODBC Driver.

 

All in all, why is a MS product so poo that ti want to lock a whole table for a select. If you need to lock a table that way it should be down to the user.

 

 

Thanks for the reply though.

[grahamc]

have a look for something like with (nolock), it works in sql.

 

there are reasons for locks

 

sysbase... get a real ms product MSSQL

[MrRalphMan]

I get what I am given.. Just glad it's not an Access db.. lol

[grahamc]

http://groups.google.com/group/sybase.public.powerbuilder.database/browse_thread/thread/234fbf1353848f53/8524a503742e359c?lnk=raot&hl=en

 

nolock table hint

[MrRalphMan]

Hi all,

 

Thanks for the advice, does this get set in the SQL statement?

I've been talking to our DBA's and they cannot get it to work without locks.

I know locks are there for a reason, but if I lock our live reporting DB again for 20+ mins, I'll get shot...