I don't have a solution but an alternative...

I do quite a similiar thing. I have an app that runs 24/7 unattended. After midnight for 5 hours is lets go of its tables so a backup can be done. Some suggestions that have worked for me well.

Switch to NT4 workstation. Much more stable. You can then go months without rebooting. If you Netware server is kicking off all of the users at night for the backup, exclude the account that the process is using so that is will remain connected. Late at night close all of the tables and other files that you are using, then in the morning open them all back up again. No need to log in out out. The NT workstation can also use the NT login as a screen saver preventing unauthorized access to the station 24 hours per day.

I happen to reboot the workstation once per month as part of a routine since I need to restart several other machines on that schedule.

Does that sound like it would work for you?

>We're near the end of developing a generic batch VFP process that will run on a PC workstation under Win95 attached to a Novell 4.x LAN, using Novell Client32 v.3.1, running unattended essentially 24 x 7... The process 'goes to sleep' during nightly backups -- with only a time-setting table open, so assure maximum availability of files for current backup activities.
>
>Our old DOS batch processes all re-boot themselves after 'waking' back up in the morning, to assure fresh network connections, and also reboot upon fatal errors (like 'not a database file' and stuff like that, that is otherwise hard to recover from without user intervention. In the DOS world, the Autoexec.Bat file starts, invokes the DOS login command -- with a saved username and no password -- so it just blows by with no user intervention needed, then invokes the FP runtime for the batch process, then when the FP process exits, it runs a DOS ColdBoot.Com executable that restarts the system.
>
>We have added a WinAPI call in our VFP app that will gracefully shutdown both VFP and Windows -- ie: "Restart the computer". The problem is that our Novell Windows Client login dialog requires pressing/clicking the "OK" button, even if there is no password. Without the ability to bypass that step, our re-boot/freshen environment technique is no good.
>
>Any ideas on a either a replacement for the Novell Client login that does not need the "OK" button if no password, or a way to 'stuff the keyboard' or something else??
>
>TIA
>
>Rob