>>So what you're saying is that the servers have no standardized directory structure and that the app could end up anywhere on the server. Therefore, even by checking the mapped network drives you couldn't reliably retrieve the location of the app without searching the entire drive. If this is correct, I can see the problem and how it'd be difficult to use a post-setup executable to do this work.
>
>Yes, the server admins can actually rename the primary folder, place anywhere, share or not share, map or not map, whatever they wish, it's ultimately flexible. I may try to get it approved as a Bureau Standard application, then we would standardize the setup, and put it on the Intranet. But that means a major testing, certification, & red-tape process, so...I'm kind of waiting for the LAN powers to come courting me, since this is a nice timekeeping application almost everyone uses. If that occurs, they will bypass a lot of the red-tape. We had about 3 different ones, done in VB and Access also, but the others died at the Y2K turnover, so now my vfp app has gone much wider, just kind of spread around by word-of-mouth. Too bad I get no royalties :)

About the only thing you could do in this situation would be a PUTFILE() type scenario and ask whoever's installing the program to point to the executable. I've been there, unfortunately, and the percentage of misses is higher than the hits.

Too bad about the royalties though< s >.