Tim,

I moved my first application to EDB successfully and it was fast and without
problems (I also succeeded to replace DBISAM's reverse-engineering code to
Delphi with SQL in similar way that enables table creation and version table
structure changes as well). When I wanted to test it with remote access I
found the problem with extensions.

Because I have all EDB tables in same directory I found that modified
extensions are more readable if I omit the EDB string in first three
positions of extensions. Using this is ok in local mode.  When I apply the
same modification to remote access (to local IP for the beginning) the
configuration file is not found and the new one is created with default
extension.

I have the following extension modification:
 if not engine.Active then with engine do begin
   ConfigPath := 'c:\kresEDB\EDB';
   CatalogName := 'EDB';
   BackupExtension :=  '.bkp';
   CatalogExtension :=  '.cat';
   ConfigExtension :=    '.cfg'; ... and so on

What did I not use in the right way to make the same extensions in remote
databases?

The EDBManager does not allow to make extensions different as default ones
if I set the session to rfemote acces - it simply hides the Local
Customization Tab. How to cope this? If it is not possible to use it in
remote access it seems to me that the possibility of chainging table
extensions is pracically useless.

Regards
Iztok Lajovic

Iztok,

You have to apply these settings not to your client engine or EDB Manager, but to the server.

If you start edbsrvr.exe, right-click the icon, click "Restore" -> "Stop Server" -> "Edit
Server Options" there is a "Customizations" Tab in which you can set your extensions.

Heiko

Heiko,

thank you for your advice. I know for this possibility but I need automated
way to install the server (starting it as net service can be done by
administrator at site). I wonder if there is a way to programatically change
all other characteristics as configuration file name and table extensions
before the server is started.

Iztok Lajovic


"Heiko Knuettel" <heiko@knuettel.com> je napisal v sporoèilo
news:FBCA4C66-FE60-48DA-8D10-B5D1AFE39106@news.elevatesoft.com ...
> Iztok,
>
> You have to apply these settings not to your client engine or EDB Manager,
> but to the server.
>
> If you start edbsrvr.exe, right-click the icon, click "Restore" -> "Stop
> Server" -> "Edit
> Server Options" there is a "Customizations" Tab in which you can set your
> extensions.
>
> Heiko
>

Iztok,

you can use the command line server (edbcmd), and pass the settings you want with an ini
file. You can take a look at the edbcmd source to see how that ini file should look like.

Maybe this works with edbsrvr too, but I don't know for sure, and I can't find anything in
the manual.

Or you can create your own customized server - that is as easy as placing the TEDBEngine
component on a form, and setting EngineType to etServer.

Heiko

Heiko,

I will look at source of command line server.

I just wanted to deploy the original server otherwise I have to change it
every time when new version comes.

Thank you
Iztok Lajovic

"Heiko Knuettel" <heiko@knuettel.com> je napisal v sporoèilo
news:31EB1C15-A3F4-437A-97CC-9D73F912B000@news.elevatesoft.com ...
> Iztok,
>
> you can use the command line server (edbcmd), and pass the settings you
> want with an ini
> file. You can take a look at the edbcmd source to see how that ini file
> should look like.
>
> Maybe this works with edbsrvr too, but I don't know for sure, and I can't
> find anything in
> the manual.
>
> Or you can create your own customized server - that is as easy as placing
> the TEDBEngine
> component on a form, and setting EngineType to etServer.
>
> Heiko
>

Heiko,

<< Maybe this works with edbsrvr too, but I don't know for sure, and I can't
find anything in the manual. >>

Yes, it does.  The .INI file settings are discussed here:

http://www.elevatesoft.com/manual?action=mantopic&id=edb2sql&category=0&topic=3

--
Tim Young
Elevate Software
www.elevatesoft.com