In my case everything is a free table at least I assume it is. I am doing a custom report on data from a system that was done in VFP where the developers tried to mask the fact that it uses VFP tables. (They use a ."udb" extension but left the ".cdx" extension alone.) All I needed to do was use the full filename in the select statement.
I don't understand how I could be using different data sessions if the same code is executing. Is there something different in the environment when code is executed from the command line versus called from another program? Joe On Friday, April 03, 2009 2:59 PM, Tracy Pearson wrote: > >Date: Fri, 3 Apr 2009 14:59:20 -0400 >From: Tracy Pearson >To: [email protected] >cc: >Subject: RE: Different SQL Select results from Command line versus >anapplication > >Different Data Source >In the DBF world, a corrupt index could be the culprit. > >-----Original Message----- >From: Joe Yoder >Sent: Friday, April 03, 2009 2:58 PM > >I have a .prg with an SQl select statement that builds a table from several >others. When I run the .prg from the command line, the output table has the >expected data in all fields. When my application calls the same .prg either >as an application or as an executable, one of the fields in the first record >comes back blank. What could be causing this? > >TIA - Joe > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
