Had a very similar situation and found if I ran views against the 2.6 tables I could denormalize them into something that made sense, create interface and querying stuff the users loved and massage the data with VFP before priting. Also a good way to begin migrating an app and to convince the client that there are a lot of really nice perks to writing an upgrade. ( put in XFRX and WinIPStuff and start eamiling pdf reports automatically and you'll have them eating out of you hand :-)
>I really don't want to but think I have to :)
>
> I have a 2.6 app that somebody wrote an external printing module in Visual. The problem is that the 2.6 app is a payroll application and they are passing the check printing off to the visual app. This is causing all sorts of problems with tables not being closed before the visual app try's to open them and code pages changing on tables etc.. The reson they did this was to get the app to print on Windows XP as the original 2.6 code was not using report forms instead it was creating a text file and using the ??? command to write it to lpt1 which doesnt work under 2K or XP.
>
> So I was hoping I could convert the existing reports back to 2.6 rather than recreating them as a 2.6a report form will print just fine under XP so there is really no reason to have an external printing program.
>
>Paul
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.
