Cindy,
thanks for your reply. Here's where I am at this point:
I've found that there are some tables that are indeed not
compatible with ODBC. My predecessor (whose app I'll be
replacing) used a VB script to get those copied and saved
in a previous version. Not sure how he did that without
any loss of information, but apparently there's a VB
method that does that.
I was hoping to just go the OLE DB route and get the
information into SQL Server - seems like that will be a
feasible route. Would you recommend setting the FoxPro
tables up as linked tables in MSS?
More pressing for me at this point, however, is another
issue - is there a user friendly query client for Visual
FoxPro 7? I'd love it if I could use something similar to
Query Analyzer in MSS2000 that has an object browser so I
can do ad hoc queries and get more familiar with the
database, plus be able to actually test the sql I'll be
using to retrieve data in real time. Anything like that
available? The query functionality in Visual FoxPro 7
seems to require that one build a project first - seems
like a lot of overhead. Am I overlooking something there?
Thanks,
Andreas
[quoted text, click to view] >-----Original Message-----
>Hi Andreas,
>
>Over the years new features have been added to FoxPro
tables. Tables using
>features that were added in VFP7 and above are not
accessible via ODBC (they
>are accessible via OLE DB). However, just because an
application was written
>with VFP7 (or above) doesn't mean that the new data table
features have been
>used. To determine whether ODBC will work (that no post-
VFP6 features have
>been used), try something simple like linking the tables
to an Access
>database via ODBC.
>
>
>--
>Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
>cindy_winegarden@msn.com
www.cindywinegarden.com >
>
>"Andreas" <a_macke@yahoo.com> wrote in message
>news:0e2c01c4a590$c13360e0$a601280a@phx.gbl...
>> I'm looking to build an application that will get data
>> from an HR system (built in Visual FoxPro 7.0), import
it ......
>> I assume that
>> should be possible, given that there's an odbc driver
for
>> Visual FoxPro.
>
>
>.
Hi Andreas,
I'm sorry to say I don't work with SQL Server enough to give you good advice
on the best way to access your Fox data via SQL Server.
A project isn't required to do queries - use File > New > Query. However, a
creating a project and adding all the pieces to it is a great way to have
everything readily at hand even if you're not building an application.
If you're more comfortable with SQL Server Query Analyzer then you may be
able to use a linked server to connect to your data, but again I'm not a SQL
guru and I don't have SQL2K on this machine to try it out.
Maybe someone else will have something to offer.
--
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@msn.com
www.cindywinegarden.com [quoted text, click to view] "a_macke@yahoo.com" <anonymous@discussions.microsoft.com> wrote in message
news:1ce701c4a737$34e3f110$a401280a@phx.gbl...
> .....I was hoping to just go the OLE DB route and get the
> information into SQL Server - seems like that will be a
> feasible route. Would you recommend setting the FoxPro
> tables up as linked tables in MSS?
>
> More pressing for me at this point, however, is another
> issue - is there a user friendly query client for Visual
> FoxPro 7? I'd love it if I could use something similar to
> Query Analyzer in MSS2000 that has an object browser so I
> can do ad hoc queries and get more familiar with the
> database, plus be able to actually test the sql I'll be
> using to retrieve data in real time. Anything like that
> available? The query functionality in Visual FoxPro 7
> seems to require that one build a project first - seems
> like a lot of overhead. Am I overlooking something there?