Subject Re: ExportData.wfm problem
From Pieter van Heerden <psvh@mweb.co.za>
Date Sat, 12 Jul 2014 04:19:44 -0400
Newsgroups dbase.getting-started

I have tried copying the first query to a second table and using that table, because at one stage I got the impression that a query involving more than one table could also lead to problems in the ExportData.wfm.  No such luck.

I have also copied the query results to a table to see If there is anything "funny" in the results.  No such thing, the result of the queries I did ended up as perfectly normal query results.

My problem remains that ExportData.wfm opens as expected, the query results are loaded and shows in the selection pane, but on selection of fields, the result pane shows the field name (column heading) but the content of the field does not show, and therefore no export can take place.

At one stage during my testing an error message appeared on opening of the ExportData form:  "Problem creating Excel OLE Autoclient object.  Exporting to Excel may work, and it may not."  Whether this has anything to do with the problem I experience, I do not know.




Kurt Wrote:

> You are Lucky, I upgraded to Plus9 and the SQL command q.sql = "@Example" throws up an error. This is how I do it, it's probably wrong, but it works for me.
 >
> q = new QUERY()
 > q.sql = "SELECT * FROM Abn A INNER JOIN Customer C ON (A.CUST_NO =C .CUST_NO)"
 > //q.sql would be your exportwuasub.sql
 > q.active = true
 > u = new updateset()
 > u.source = q.rowset
 > u.destination = "temp.dbf"
 > u.copy()        
 >
> Pieter van Heerden Wrote:
 >
> > This is dBase 2.8 on Windows 8.
 > >
> > I have a problem with the exportdata form in that it does everything expected, up to the point where selected fields have to be "filled" with data.  Column headings show, but the contents remain empty.  
 > >
> > Removing a column from the list is successful, trying to add a column that shows is unsuccessful, with an error message to that effect.  This is behavior as it should be.
 > >
> > The query from which export is done is:
 > >       d = new database("SAPWAT")
 > >       d.active = true
 > >       q = new query()
 > >       q.database = d
 > >       q.sql = "@exportwuasub.sql"
 > >       q.active = true
 > >       do ExportData.wfm with q
 > >
> > The number of columns to be exported is 72 and the number of rows about 700.  I have reduced columns to 20, made no difference so there does not seem to be an overload of data.
 > >
> > The end result is that although the query is successful, no export can take place.
 > >
> > Is there an alternative that I could build into my application, or does someone have an answer to my problem.
 > >
> >
> >
>