🚀 go-pugleaf

Mark,

You've entered the fantastic world of ADO.

I'll advise to read the descriptions of Borland and MS of the ADO features
very thoroughly when it comes to properties like CursorLocation, CursorType,
LockType etc. Myself for example I am still struggling with developing a
robust lockmechanism.

Reading lot's of newsarticles the general purpose of ADO looks to be to
support remote access to databases, for example through new technologies
like webservices. The general idea is to use client-cursors in a
client-server environment.

MS Access does support server-side cursors but this seems to be kind of
faked since MS Access is a file-based engine. MS SQL Server also supports
server-side cursors but the advise is not to use them. There are other
problems you could get using server-side cursors. DBGrids for example don't
work anymore because bookmarks are not supported.

Using large recordsets my experience is as follows:
With a client-side cursor the loading of the recordset takes lots of time.
After that the performance is good when stepping through the recordset. With
a server-side cursor the first records are displayed very fast, but stepping
through the recordset takes lots of time (Locate() etc..)

Keep your recordsets as small as possible.

--
HTH

Ronald Loonstra
CodeFit Applications
www.codefit.nl

"MarkR" <mark.richards8@wapthespamntlworld.com> schreef in bericht
news:3dae8e59$1@newsgroups.borland.com...
> Hi,
>
> I have tried that, but then the cursortype changes from ctDynamic to
> ctKeyset, which stops changes by other users from being seen.
> Is it that MSAccess doesn't support multiuser connections?
>
> "Vassiliev V.V." <news@vassilievvv.mtu-net.ru> wrote in message
> news:3dae5668@newsgroups.borland.com...
> > Set CursorLocation to clUseServer on TADODataSet (TADOQuery, TADOTable
> > etc.).
> >
> > ----------------------------------------------------------------
> > Regards,
> > Viatcheslav V. Vassiliev
> > http://www.oledbdirect.com
> > The fastest way to access MS SQL Server and MS Jet (MS Access)
databases.
> >
> > "MarkR" <mark.richards8@wapthespamntlworld.com> �������/�������� �
> ��������
> > ���������: news:3dad20d3@newsgroups.borland.com...
> > > I am converting a simple app from paradox (using bde) to use ado and
> > > msaccess
> > > In the paradox version, I simply open the table and the app uses
> dataaware
> > > controls, including navigator bar.
> > > When i moved this over to ado and access, it now takes about 30
seconds
> to
> > > start up when i make the table active. The connection object is
already
> > > connected.
> > > It would appear that the application loads the entire contents of the
> > table
> > > into memory prior to displaying the data of the first record.
> > > Does a mechanism exist to stop this? I seem unable to get the direct
> > access
> > > like the paradox version.
> > > any help greatly appreciated.
> > >
> > > --
> > > BCB Version = 6 (sp2) Professional
> > > O/S Windows XP Prof
> > > ------------------------------------------------------
> > > "There are 10 types of people in the World, those that understand
> binary,
> > > and those that don't."
> > > [Thanks to TheFatBoy-UMD]
> > >
> > >
> >
> >
>
>