1.04b5

Tim,

Starting the server, starting a client app. Then kill the session by
stopping the server. Trying to start the server again results in an AV.

Also it seems that I can only start the client app four times (same
machine). Is the 5th (VCL standard) session reserved for Admin use? (could
not find it in the manual) The 5th times the app "starts" with a Win error
screen (all components are set to active). Maybe an EDB error would be
preferable such as "max sessions used"

A little question about refreshing: when in edit mode htting the refresh
button (DBnavigator) saves the changed record first. Is this common VCL
Dataset behaviour -did not notice it before?

Regards, Harry

Harry,

<< Starting the server, starting a client app. Then kill the session by
stopping the server. Trying to start the server again results in an AV. >>

Got it.   A fix will be in the next build.

<< Also it seems that I can only start the client app four times (same
machine). Is the 5th (VCL standard) session reserved for Admin use? (could
not find it in the manual) The 5th times the app "starts" with a Win error
screen (all components are set to active). Maybe an EDB error would be
preferable such as "max sessions used" >>

The Windows error instead of the EDB error is due to the components being
set to True at design-time.   EDB is still raising the same exception, but
it is getting converted into a runtime error because the Application object
hasn't been started yet.

<< A little question about refreshing: when in edit mode htting the refresh
button (DBnavigator) saves the changed record first. Is this common VCL
Dataset behaviour -did not notice it before? >>

Yep, common behavior.  The navigator uses the TDataSet.CheckBrowseMode call.

--
Tim Young
Elevate Software
www.elevatesoft.com