>I just wanted to warn everyone about a problem I have run into. I have already corrected it, but it was annoying. I have a VFP5 program that uses Crystal Report Writer so that the client can create their own invoices. Don't ask me why we don't use the built in report writer as that decision was out of my control. Anyway, I originally had a VFP 5.0 dbf that is copied to a foxpro 2.5 dbf that is tied to all the Crystal Reports. For whatever reason, the VFP 5.0 dbf kept getting corrupt so I decided to start using a temporary dbf in its place. However, when I set up the temporary dbf, I did not put the fields in the same order so the foxpro dbf that is creaed from this file also had its fields in a new order. When I went back and ran the reports, the variables all showed values belonging to another variable. Apparantly, CRW ties itself to a field location or number and not to a field name. It is not a huge problem, but I thought I would pass it on so that I can perhaps help
>someone avoid headaches in the future. Once I put the fields in the same order, everything worked just fine.
>
>Jason Mower
>Technical Edge

I've seen this too. It has nothing to do with VFP. It's the way CR works.