I have an app for managing an annual golf event that I wrote and distributed in 2000 using Paradox 9 Developers addition. The distributed runtime app has been used exclusively on a Windows 98 laptop, while the orginal app still runs on a windows 98 desktop. Recent attempts to migrate to a newer desktop machine running XP professional have failed in one respect: reports. All other app features appear to perform correctly. Some of the reports run OK, some run but show no data, one appears to mix header fields with detail report band fields.
The form of migration was installation of Paradox 9 on the xp machine, then copying over all app files and directories. Some clues:
Re: a report that shows the team make-ups for each day of the event, grouped by day. The detail is a table frame displaying teams by number. One table is in the data model. The report runs but shows no data, although the underlying table exists and displays correctly. Attempts to recreate the report using the expert produces and error (i.e. expert fails). I can recreate the report using the data model, but the report fails when I add the group band (pdox gives a linking error?). But, I can recreate the report if I first recreate the underlying table manually. (Normally the base report table is recreated by the app each time the report is called. I notice that the copied over table is only 6K in size, while the new, manually created table is 18K??
Note: I did use the table utility to restructure any table not in Pdox 7 format in the orginial app.
Any ideals how to make this migration work?
Addl info: The report expert runs in a new directory on the xp machine, but not in the copied over directory. It's as though some necessary file or files are missing from the restored working directory, but what? What does the substantial differences in .db file size for the source table mean?
S
Client
Print This
