Re: ODBC or OLE DB
- From: "Bernie Beattie" <BernieBeattie@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 19 May 2005 05:57:41 -0700
I'm using Native for the cursoradapter with VFP backend, and ODBC for the
cursoradapter with SQL backend. I see now that I could have chosen ADO with
SQL and that would then use the OLE DB connection string but would that mean
I end up with ADO recordsets being returned? I wouldn't want those. I need
to have normal cursors.
What I'm trying to do is use a consistent way of interfacing between our VFP
application and the data, and Crystal reports and the data.
"Cindy Winegarden" wrote:
> Hi Bernie,
>
> I'm confused. Are you working within FoxPro to connect to either Fox tables
> or SQL tables? If you're using CursorAdapters, what are you using for your
> data source type? (Right click on the CA > Builder > Properties tab) If you
> choose ADO and then Connection string, both the VFP and SQL Server OLE DB
> providers should appear in the list of choices on the Provider tab.
>
> You could have one CA and then just change this property when you
> instantiate it.
>
> --
> Cindy Winegarden MCSD, Microsoft Visual Foxpro MVP
> cindy_winegarden@xxxxxxx www.cindywinegarden.com
> Blog: http://spaces.msn.com/members/cindywinegarden
>
>
> "Bernie Beattie" <BernieBeattie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:467492D5-E15F-425F-AA0E-69FBDB844348@xxxxxxxxxxxxxxxx
> > We are trying to decide which method to use to connect reports to VFP data
> > bearing in mind that we also connect to SQL data. Our VFP8 application
> > uses
> > cursoradapters and ODBC is the only choice for connecting to SQL data. We
> > know that the VFP ODBC driver hasn't been updated for years and doesn't
> > cope
> > with the new autoincrement field type but as we don't use these types of
> > fields, we are tempted to stick with ODBC simply so that we are
> > consistently
> > using the same method of connecting via our application and report writer
> > to
> > both datasets.
> >
> > Does anyone have any advice to suggest we shouldn't use ODBC for any other
> > reasons?
> >
> > Thanks,
> > Bernie Beattie
>
>
>
.
- Follow-Ups:
- Re: ODBC or OLE DB
- From: Cindy Winegarden
- Re: ODBC or OLE DB
- References:
- ODBC or OLE DB
- From: Bernie Beattie
- Re: ODBC or OLE DB
- From: Cindy Winegarden
- ODBC or OLE DB
- Prev by Date: Re: Centring a Form ..
- Next by Date: Using hotkeys inside a Modify Memo
- Previous by thread: Re: ODBC or OLE DB
- Next by thread: Re: ODBC or OLE DB
- Index(es):
Relevant Pages
|
Loading