Great tip.
I just converted a VFP6 app over to VFP9 within the last two weeks. So, the use of the newer VFP9 object-assisted reporting hasn't been required yet. I had to concentrate on the SQL changes which were a few more than I originally thought. I also had to be aware of a few class revisions that broke things, which I didn't expect. So, to get it all going, I liberally used SET REPORTBEHAVIOR 80 until the rest of the app now in production seems stable. Then the newer VFP9 reporting will have a better chance to get applied.
Main Topics
Browse All Topics





by: tmedleyPosted on 2007-12-20 at 08:52:26ID: 20508085
Today I answered my own question. When you use the listener class with vfp, wherever vfp is running from if there is not already an outputconfig.dbf/cdx/fpt for it to use then it will create one. In a delivered environment if vfp runtime is in system32 or some other directory that a normal user does not have rights to create files in then it will fail silently. Runnin git one time as admin creates those files. One solution to this is to deliver those files with the installation package, another is to have the package create and use the listener one time (since the assumprion is that the packahe will be run with administrator rights.