macleod
5/24/2007 3:58:00 PM
In that case, the easiest way is to stick with the current app and just tell
the client they need to insure that the server is logged in when the app
needs to run. Another option would be to continue converting it to a
service and then use Scheduled Tasks to start and stop the service.
"John" <John@nospam.infovis.co.uk> wrote in message
news:uxhQnmhnHHA.5032@TK2MSFTNGP02.phx.gbl...
> Thanks. The other problem is that when server is logged off to avoid
> unauthorised access then application is closed until someone logs back in.
>
> Regards
>
> "Charlie Brown" <cbrown@duclaw.com> wrote in message
> news:1180016226.049844.41700@p77g2000hsh.googlegroups.com...
>> On May 24, 8:57 am, "John" <J...@nospam.infovis.co.uk> wrote:
>>> Hi
>>>
>>> My vb winform app updates between site sql server and in house access
>>> db.
>>> The app needs to always run and is in the start-up of client's sbs 2003
>>> (windows 2003) server. Problem is if client restart server and forget to
>>> login the app does not run. I am resisting doing it as a service as a
>>> service has some development restriction as well as installation
>>> complications making it difficult to debug too among other things. What
>>> is
>>> the best solution to this situation? Should I go the service route? In
>>> which
>>> case is there an easy way to convert a winform app (with a visible
>>> form -
>>> for monitoring purpose) to service type app?
>>>
>>> Thanks
>>>
>>> Regards
>>
>> You might be able to place a reference in the registry under
>>
>> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
>>
>> This will start software at bootup of a machine, in may be a different
>> key under SBS2003, I don't have that OS here to look at.
>>
>
>