Hi all,

Here's my situation. I have a linked server set up to connect to a
foxpro free table directory. However, it is not showing the tables.
I'm not getting any error. The DSN I have created works when I use it
in Access. So I have elimated that the DSN is set up wrong. The
tables can be connected when I connect to the Development machine.
The same set up is not showning the tables in the production machine.
The only difference between the two machines that I can see is that
the dev machine is running windows server 2000 and the production
machine is on windows NT server. Since I can hit the tables in
Access, I don't think anything is corrupted. Anyone have any
suggestions?

Would there be a problem with the latest VFP ODBC driver on the
problem machine if I can get the data using the same driver in Access?
I thought the machine with the SQL server manager would be using the
driver rather than the target machine. Is this correct?

Thanks for helping.


"Cindy Winegarden" <cindy.winegarden@mvps.org> wrote in message news:<#xEoNTwfDHA.2984@TK2MSFTNGP11.phx.gbl>...
> Do you have the latest VFP ODBC driver on the problem machine? It's
> downloadable from
> http://msdn.microsoft.com/vfoxpro/do...c/default.aspx.
>
> --
> Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
> cindy.winegarden@mvps.org, www.cindywinegarden.com
>
> "polarvonarctic" <admin@aaronwine.com> wrote in message
> news:9dee5b9c.0309191253.7de73524@posting.google.c om...
> > Hi all,
> >
> > Here's my situation. I have a linked server set up to connect to a
> > foxpro free table directory. However, it is not showing the tables.
> > I'm not getting any error. The DSN I have created works when I use it
> > in Access. So I have elimated that the DSN is set up wrong. The
> > tables can be connected when I connect to the Development machine.
> > The same set up is not showning the tables in the production machine.
> > The only difference between the two machines that I can see is that
> > the dev machine is running windows server 2000 and the production
> > machine is on windows NT server. Since I can hit the tables in
> > Access, I don't think anything is corrupted. Anyone have any
> > suggestions?