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