Solving HP 3000 challenges can sometimes be as simple as tracking the tools in your hand. Tim O'Neill, a 3000 manager never shy about asking for help, checked in on the 3000 mailing list needing help for his databases.
We would like to export all the data in a format that could be imported by Microsoft Access. Data relationships would be redefined after import. It would be nice to export, with relationships defined, that would run on Windows.
Minisoft's Doug Greenup peered over O'Neill's shoulder, as it were, sitting at his console.
Actually you own our ODBC driver which could be used for the requirement you outline. You were on support until 2009, so you have a version that handles this.The website support.minisoft.com has extensive documentation on our ODBC tool. You could also renew your support and get the most current ODBC version, along with access to our technical team to assist you.
The HP 3000 community is full of databases that need access to the world of Windows. Sometimes those 3000 servers have lightly-used tools to make the connections. As is customary for a budget-sensitive group, O'Neill's collegues on the mailing list had ideas on how to do that export without buying anything.
If ODBC is not an option, you might also try the DBEXPORT program that is available for migrations to Eloquence. By default, it writes output to "comma separated" text files (unless you use binary mode), which will likely work for importing to MS Access. The link page includes a link to the download location, including source code (so customizations would be possible).
However, using ODBC is likely better for transferring structure info.
Appel's sum-up takes note of the advantages of buying tools and maintaining support for them. Paid solutions do more, do it faster, and include access to support pros to explain how the hidden treasure can solve problems. Minisoft is still selling its ODBC solution, too.