Hello

Beside the different starting are there any functional and behavioural
differences
between edbsrvr as a service or as a application?

Thanks
Sorin

Sorin,

> Beside the different starting are there any functional and behavioural
> differences between edbsrvr as a service or as a application?

There isn't any from the point of view of how your application interacts
with the EDB server.

I'm sure that someone will correct me if I am wrong, but the only diffferent
that I can see between running as a service vs an application is on the
newer versions of Windows the icon doesn't show in the system tray when
running as a service so there is no way to start and stop the server when it
is running as a service other than using the net start and net stop
functions.

--

---------------------------------------
 Terry Swiers
 Millennium Software, Inc.
 http://www.1000years.com
 http://www.atrex.com

Now shipping Atrex 13.  For more information go to
 http://www.atrex.com/news.asp

Atrex Electronic Support Options:
 Atrex Knowledgebase: http://www.atrex.com/atrexkb.asp
 Email: mailto:support@atrex.com
 Newsgroup: news://news.1000years.com/millennium.atrex
 Fax: 1-925-829-1851
 Phone: 1-925-828-5892 (M-F, 9a-5p Pacific)
 ---------------------------------------

<<
Beside the different starting are there any functional and behavioural
differences
between edbsrvr as a service or as a application?
>>

I think different starting is the main difference - with service you do not need an active (console) login session to get EDB up and running. My view is that when deploying EDB on a server the service is the way to go as now if server is ever rebooted for example it will come back up automatically If you're running on your desktop while developing it should not really matter.

Running service under different user account might result in different EDB behavior in terms of being able to access files, etc but that's a Windows config issue and nothing to do with EDB itself.

With Vista/Win7/Server2008 the services model changed so you need the Interactive Services Detection service running to interact with the EDB (or better yet use EDB Manager).

Raul

<<
I'm sure that someone will correct me if I am wrong, but the only diffferent
that I can see between running as a service vs an application is on the
newer versions of Windows the icon doesn't show in the system tray when
running as a service so there is no way to start and stop the server when it
is running as a service other than using the net start and net stop
functions.
>>

It does - however you do need to use the Interactive Services Detection helper service since services architecture was changed in Vista and newer.

Once it's running you get a prompt when EDB wants to interact and you can then access Session 0 and see EDB icon and UI.

Raul