I have posted a comment before stating a problem I was having with VB and
updatebatch method and getting the error "Row Cannot Be Located for
Updating...." I have found that if I use an Update SQL statement instead
though it works fine (to do this though would be a hell of alot of extra
programming). It also used to work before and I think it was the change
from VFP 6 to VFP 7 that brought the error. Anyway, what I'm wondering is,
the VB code uses a DSN ODBC connection to VFP. I'm wondering if I use the
OLEDB connection, would this make any difference? I am also wondering what
the difference between ODBC and OLEDB is. Also I'm wondering if maybe
moving to VFP 8 would fix this problem.

Re: ODBC vs. OLEDB by Carsten

Carsten
Mon Dec 01 02:18:18 CST 2003

Altman,

OLE DB is supposed to replace ODBC, so sometime you will have to switch to
OLE DB.
VFP8 has CursorAdaptors, which handles all the "complicated" stuff like
updating records. They are a huge improvement, and absolutely worth taking a
look at.

Cheers
Carsten



"Altman" <NotGiven@SickOfSpam.com> schrieb im Newsbeitrag
news:uxWMZCctDHA.2440@TK2MSFTNGP12.phx.gbl...
> I have posted a comment before stating a problem I was having with VB and
> updatebatch method and getting the error "Row Cannot Be Located for
> Updating...." I have found that if I use an Update SQL statement instead
> though it works fine (to do this though would be a hell of alot of extra
> programming). It also used to work before and I think it was the change
> from VFP 6 to VFP 7 that brought the error. Anyway, what I'm wondering
is,
> the VB code uses a DSN ODBC connection to VFP. I'm wondering if I use the
> OLEDB connection, would this make any difference? I am also wondering
what
> the difference between ODBC and OLEDB is. Also I'm wondering if maybe
> moving to VFP 8 would fix this problem.
>
>