>>The reason I asked was that the system directory path is usually different under NT, and (while it would be just as bad) that their installation program might be putting the files in the wrong place. It appears from what you're telling me that it's strictly using the environment path string, rather than going out and retrieving the system directory from the API. That is pretty sad. However, after working some with our PB people, I'm not surprised. Their solution is to dump all the necessary files in the run time directory. This would explain a lot< g >.
>
>Good idea (well, better than what I had to do :) Maybe I'll suggest that to the PB developers as a possible solution. Or maybe they can make a separate NT version. I believe I'm the first one testing their app (and mine) under NT. I have a couple little vfp/NT GUI issues that I've posted about here to fix, too. The PB app also will have a couple little things to try and fix, most of the problems so far are color-related.

It only seems like a good idea. The number of files that are required make heavy demands in terms of disk space. Do enough PB apps and you end up with duplicate files all over the place.

>The big PB/Sybase app problem, though, is performance, under any OS. It's *real* slow, even with a small test DB. Bad design or bad tool, I don't know. The upside is, it makes my large vfp app look ultra-fast < s >

PB has always been big and slow. I've seen simple queries against the backend take seemingly forever. And forget about running one that isn't a stored procedure unless you've got totally too much time (and CPU cycles on the server) on your hands. I've heard that Sybase performs OK under something like Unix, but under Novell or NT, nope.