>>I've never had a problem getting data into Crystal. What do you need that's so different?
>
>Looking at the Visual Basic code, it seems that the thing that zinged me was the client's requirement that the program be both printer-agnostic and able to cope with any printer that could be on a given system. In order to do this, I needed information about the printers that was not available VFP, such as the printer device driver name. The program also had to be both flexible and standardized in how report choices were presented.
>
In our application we just use a printer setup menu pad which calls GetPrinter(). This has so far worked on InkJet and laser printers. Are you referrring to any other specif printer associated issues?

>VFP fit the need for standardized, flexible reports, but could not deliver the information that Crystal Reports needed for the printer-agnostic aspect. Visual Basic, however, was able to do it through the Printers collection and the Printer object. The wrapper code I use makes use of these, as well as taking care of the rest of the housekeeping that CRPE requires.

Ravi