Very very different behaviours.
Read up on MSDN on ADO cursors and locks together with SQL7.
All ADO cursors except read only, forward only, basically place some kind of
locks on the whole table(s).
Suggest you look at what is happening using the SQL query profiler - rather
frighting stuff when cursors are in use. You will see why your App is so
slow.
You have to remember with ADO that the cursor and lock combination tell ADO
what you are going to do with the RETURNED recordset (not what to lock use
on the server side - ado makes up it's own mind about that).
>From memory the client side cursor is the only one that can be used in a
grid with Delphi (yuk).
Myles.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 15, 2000 2:41 PM
To: Multiple recipients of list database
Subject: [DUG-DB]: ADODataset and Cursors
Hi,
I have a Delphi5E(patch1 applied) MSSQL7 application and ADODataset.
Our App was running extremely slow and we changed the Cursor location to
Server side for the ADODataset. this made the app run extremely fast and we
are very happy. But using the server side cursor seems to have a mind of
it's own. some D5E applications are ok others won't have the cursor location
set to server and will only accept client as a setting on the same
development machine and same SQL server.
Are there any special things to note when seting Cursor locations on the
server or client.
Thanks for any input
Jason Webb
---------------------------------------------------------------------------
New Zealand Delphi Users group - Database List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Database List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
