Re: ADO Recordset Cache

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Bill Morgan (willmorgan_at_liso.com)
Date: 05/06/04 

Date: Thu, 6 May 2004 13:02:37 -0700

oops. I didn't mean without using any "data access
objects" - I meant without using any data controls (i.e.
in VB, withou using ADODC, etc.)

Bill

>-----Original Message-----
>Neil,
>
>I would really like to take a look at what you've created
>so long as I am able to see the source code.
>
>What I am looking for is a VB/db interface example that
>allows simple navigation through a db (just like a bound
>form with bound text boxes in Access), but which does not
>use any of the data access objects. In other words, it
>works based solely on VBA/ADO or VB/ADO code.
>
>Basically, I am probably having a conceptual problem.
>Using only VBA/VB/ADO code I am having trouble seeing how
>developers would give the appearance of a "persistant"
>database that I can walk through, moving back and forth
>through records.
>
>Thanks again for all your help.
>
>Bill Morgan
>willmorgan@lisco.com
>
>
>
>
>
>
>
>>-----Original Message-----
>>Hi Bill,
>>
>>I was reading this post and the situation was sounding
>very familiar - then
>>i saw your name by the side of your post :-)
>>
>>In previous posts about your ADO nightmares, I believe
>you mentioned you
>>were learning VB. If you have access to Visual Basic 6,
I
>could email you a
>>sample of what you are trying to do. I created a very
>basic sample program
>>for a freind (1 form with a few fields that link to an
>Access database using
>>ADO) who was also having problems with getting to grips
>with this. It's a
>>zip file that is 31KB in size. It contains the VB
project
>with forms and the
>>access database along with the .exe of the program that
>you can mess about
>>with.
>>
>>Let me know,
>>
>>Neil.
>>
>>"bill morgan" <willmorgan@lisco.com> wrote in message
>>news:933501c4336b$54877fe0$a601280a@phx.gbl...
>>> I am trying to get a more in depth understanding of
ADO.
>>>
>>> Does anyone out there happen to know what general
>>> programming scheme lies behind the MoveNext navigation
>>> button on a bound form?
>>>
>>> All of the ADO routines I have written create a
>recordset
>>> and then destroy the recordset within the same Sub
>>> Procedure. So I can loop through a recordset, or
>MoveNext
>>> or MovePrevious a pre-determined number of records,
but
>I
>>> haven't yet produced the effect of moving back and
forth
>>> through a recordset, one record at a time, as with a
>>> navigation button on a bound form.
>>>
>>> How does a bound form MoveNext button acheive the
effect
>>> of moving sequentially back and forth through records?
>>> Does it pass a Bookmark or AbsolutePosition or
>other "key"
>>> value to a modular level variable in order to remember
>>> from what record it is moving from the next time the
Sub
>>> Procedure is run?
>>>
>>> Thanks for any knowledge you have in this area.
>>>
>>>
>>
>>
>>.
>>
>.
>

Quantcast