Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP.exe running without logged in user
Message
General information
Forum:
Windows
Category:
Administration & Security
Miscellaneous
Thread ID:
00400166
Message ID:
00401275
Views:
24
< snipped >
>Larry,
>
>I've noticed that there seems to be a problem because it requires the use of a session to show the screen. Let me give you a little background to clarify...
>We have a download that takes text data and brings it into our VFP system. Currently the download is fired by manual intervention and this is what we were trying to get rid of. So what I tried to due was use a shell program that would bring up the screen and fire it automatically using the click event of the already existing button.

If you are downloading something, why do you need the screen in the first place? Is it to show progress? From your post, it doesn't seem to be the case because you want to be able to schedule it and a user may or may not be logged in.

>So can I do this without a logged in user? I've tried using the /interactive parameter but still don't seem to have much luck.

The /interactive parameter causes the AT command to use the currently logged in user (if one exists) for reporting/authentication purposes. It doesn't log a user in. If none exists, the SYSTEM account is used.

>
>Maybe I need to redesign so that a screen isn't necessary by bringin all the code into classes that can run with or without the screen? If this is the answer, then do I have to do something to suppress the main Visual Foxpro window as well?

You can create a CONFIG.FPW file and compile that directly into the EXE/APP. Have SCREEN=OFF in the file. That is the minimum. When the app starts, there will be no visual manifestation of VFP. This suppresses the entire VFP session. You can accomplish near the same thing by adding _Screen.Visible = .F. near the beginning of your top-level program. VFP will initially start visibly but will disappear very quickly (flash effect).

>
>As for the UNC's I agree, but isn't that still going to require authorization to get to the resource on another machine? I.E, after I loginn I can access the resource on another server because my machine sends the login/pass from the local environment to authenticate to the other server... so if no one is logged in will it work? Or is that what you mean by AT uses the SYSTEM user which should have rights to the other server?
>

The SYSTEM user is not authenticated on any other server except the local machine. You do have to authenticate a valid user if the path is on a separate machine. That's where Ed Rauh's classes come in. With that you can use the WNetAddConnection2 WinAPI function to specify a remote path, authenticating user and password. Everything would be done programatically.
Larry Miller
MCSD
LWMiller3@verizon.net

Accumulate learning by study, understand what you learn by questioning. -- Mingjiao
Previous
Reply
Map
View

Click here to load this message in the networking platform