Re: Recordset.open with existing Records in the DB

ghosthunter_at_gmx.at
Date: 01/18/05 

Date: 18 Jan 2005 00:28:20 -0800

I .close the objects wenn finishing der Program, but I don't set them
zu Nothing, will try this one but I think that will change nothing.

I took a look on my Recordset (with Cursortype=client and
adOpenDynamic)

rszahlung->ActiveConnection->Cursorlocation = adUseServer
rszahlung->Cursorlocation = adusClientBatch
rszahlung->CursorType = adOpenStatic

and after the .open I get 2Errors in
rszahlung->ActiveConnection->Errors

1.
Error Number: -2147217887
Error Message: Multiple-step OLE DB operation generated errors. Check
each
OLE DB status value, if available. No work was done.
Error Source: Microsoft OLE DB Provider for ODBC Drivers
2.
Error Number: -2147217887
Error Message: The provider does not support the property.
Error Source: ADODB.Connection

rszahlung->PageCount & rszahlung->Recordcount: The E_FAIL Error from my
1st Post.

Stephen Howe wrote:
> "Gh0st" <ghosthunter@gmx.at> wrote in message
> news:25c9c5e0.0501130257.3d31a243@posting.google.com...
> >I have a strange Problem.
> >
> > If i open my empty DB an read the Recordset, make some AddNew und
> > Update it everythink works fine.
>
> Are you sure? Perhaps the problem is here at this point.
> Hypothesis : Perhaps you are not closing your Recordset and
Connection
> properly after doing the update the 1st time and when you restart the
2nd
> time the DB "knows" this. It is a possibility.
>
> When you have finished with the Recordset & Connection object you
should
> have
>
> rsZahlung.Close
> Set rsZahlung = Nothing
> conBeweg.Close
> Set conBeweg = Nothing
>
> > rsZahlung.CursorLocation = adUseClient
> > rsZahlung.Open "SELECT * FROM CIRHERZAHLUNG", conBeweg,
adOpenDynamic,
> > adLockOptimistic, adCmdText
>
> You will never get this CursorType. ADO is allowed to coerce
CursorType and
> LockType into something else if the requested type is not available.
You can
> print out what you did get _AFTER_ a successful Open().
>
> For client-sided cursors, CursorType is always adOpenStatic. If you
want the
> other cursor types (which are subject to Provider and query), it has
to be
> server-sided.
>
> Stephen Howe

Relevant Pages

  • ADODB.Recordset.Bookmark
    ... recordset does not support them and that it may be the fault of either the ... what cursortype I should be using. ... The provider is MS SQL Server. ...
    (microsoft.public.vb.database.ado)
  • Re: recordset.save takes too long!
    ... the Save Method "saves the Recordset in a ... the configuration I developed under fails to perform well at the client site ... The CursorType does affect performance. ... Using adOpenKeyset or adOpenStatic would be better ...
    (microsoft.public.vb.general.discussion)
  • Re: CursorType, LockType von ADO-Recordsets
    ... Use the CursorType property to specify the type of cursor that should be used when opening the Recordset object. ... If an unsupported value is set, then no error will result; the closest supported CursorType will be used instead. ...
    (microsoft.public.de.access.clientserver)
  • Re: Cursors - Server Side - Only Forward?
    ... >Hi Gerard, ... the .CursorType ... >have to create a recordset yourself and execute the SQL ... >> Gulf Management Systems ...
    (microsoft.public.sqlserver.programming)
  • Re: Recordset.open, with SS2005, changes CursorType to adOpenStatic
    ... server-side code should *never* explicitly waste compute, ... I open the Recordset with adOpenDynamic CursorType. ... and will never be stored in a table on the server? ...
    (microsoft.public.data.ado)