It seems that EDB does include many useful helper functions. F.ex., by accident I found
the function StripFilePathAndExtension, which is located in the EDBFileMgr unit. I assume
there are more such useful functions? Where can I find some documentation about them?

BTW: I am using the EDB error constants. However, they are not defined in the EDBConsts
unit as stated in the doc, but in the EDBError unit. this took me some time and nerves to
find out... Please update your doc.

Best regards
Stephan Krämer

Stephan,

<< It seems that EDB does include many useful helper functions. F.ex., by
accident I found the function StripFilePathAndExtension, which is located in
the EDBFileMgr unit. I assume there are more such useful functions? Where
can I find some documentation about them?  >>

There are many functions like that in EDB, but they are internal to the
engine and are not documented.

<< BTW: I am using the EDB error constants. However, they are not defined in
the EDBConsts unit as stated in the doc, but in the EDBError unit. this took
me some time and nerves to find out... Please update your doc. >>

Where in the manual does it say that they are in the EDBConsts unit ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,


>>>There are many functions like that in EDB, but they are internal to the
engine and are not documented.

But you yourself are citing such functions in your support herein. This is exactly how I
found the StripFilePathAndExtension function. Anyone who has the source code, can use
them. I feel somewhat discriminated if you don't publish this in suitable form to standard
users also.


>>>Where in the manual does it say that they are in the EDBConsts unit ?

Under Getting started
>>>>>>
Exception Handling

The most basic form of exception handling is to use the try..except block (Delphi and
Kylix) or try..catch (C++Builder) to locally trap for specific error conditions. The error
code that is returned when an open fails due to an exclusive lock problem is 300, which is
defined as EDB_ERROR_LOCK in the edbconsts unit. The following example shows how to trap
for such an exception on open and display an appropriate error message to the user:
<<<<<<<<


However, I am sorry not to have read the introducing text in Appendix A. I remember I read
this in earlier builds so I did not pay attention to that anymore. It is quite hard do
deal with your many builds.... It seems that everything needs to be reread again with a
new build because something could have been changed or added?


Best regards
Stephan Krämer

Stephan,

<< But you yourself are citing such functions in your support herein. This
is exactly how I found the StripFilePathAndExtension function. Anyone who
has the source code, can use them. I feel somewhat discriminated if you
don't publish this in suitable form to standard users also. >>

The operative words here are "anyone who has the source code".  Just because
something is in the source code to the engine does not mean that we are
obligated to document it and make it available for outside use.  Much of the
engine is not intended to be used in any other context, therefore we don't
encourage such use or document it as such.

<< The most basic form of exception handling is to use the try..except block
(Delphi and Kylix) or try..catch (C++Builder) to locally trap for specific
error conditions. The error code that is returned when an open fails due to
an exclusive lock problem is 300, which is defined as EDB_ERROR_LOCK in the
edbconsts unit. The following example shows how to trap for such an
exception on open and display an appropriate error message to the user: >>

Thanks.  I searched around and couldn't figure out where you saw this.

<< However, I am sorry not to have read the introducing text in Appendix A.
I remember I read this in earlier builds so I did not pay attention to that
anymore. It is quite hard do deal with your many builds.... It seems that
everything needs to be reread again with a new build because something could
have been changed or added? >>

Very rarely does the documentation change between builds, and if it does it
is simply because of a typographical error like what you found.   Any time
functionality changes at all, we make it a new release, not just a new
build, and the release notes that come with the email that you receive and
with the product installation itself document what has changed or is new.
Builds are reserved for bug fixes only.

--
Tim Young
Elevate Software
www.elevatesoft.com