Tim,

I am still hoping for the vesion of EDB which can be used with the current vesion of
Lazarus/fpc. Is it still tied to the release of  EDB v2.03?
(Tried to check it in the download section but the version of the  available trials can
only  be seen after login.)  

Regards, Leslie

Leslie,

<< I am still hoping for the vesion of EDB which can be used with the
current vesion of Lazarus/fpc. >>

This has been available for a couple of months now:

http://www.elevatesoft.com/incident?action=viewrep&category=edb&release=2.02&type=f&incident=2860

We don't have a trial version anymore because of the issue mentioned in the
above incident report.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

<<This has been available for a couple of months now ...

We don't have a trial version anymore because of the issue mentioned in the
above incident report.>>


1. Do you have feed back from costumers succesfully using EDB in ARM-WinCE projects? (The
earlier version(2.0.1b4) you have provided for me  for testing worked for Win32 target
with simple tests but I got #504  when opening a session  under WinCE.)

2. Currently the only avalable version on  the order page is  EDB-LCL-STD-SRC. Earlier
there was a full source LCL version too for the same price. I would like to ask if there
will be a full source LCL  version available again? If yes, when and for what price?


Regards, Leslie

Leslie,

<< 1. Do you have feed back from costumers succesfully using EDB in
ARM-WinCE projects? (The earlier version(2.0.1b4) you have provided for me
for testing worked for Win32 target with simple tests but I got #504  when
opening a session  under WinCE.) >>

That's a normal error message in most cases.  Were you trying to access a
configuration/database directly on the WinCE device ?  And, if so, are you
sure that you didn't have any other processes running that were already
using the same configuration ?

<< 2. Currently the only avalable version on  the order page is
EDB-LCL-STD-SRC. Earlier there was a full source LCL version too for the
same price. I would like to ask if there will be a full source LCL  version
available again? If yes, when and for what price? >>

I assume that you're referrring to the EDB-LCL-CS-SRC version ?  Right now
the only way to compile the unlimited ElevateDB Server is with Delphi, so if
that is what you need, then you should order the EDB-VCL-CS-SRC product for
that (or the EDB-VCL-CS product if you don't need the source code and just
want the unlimited ElevateDB Server).   The EDB-LCL-STD-SRC product is only
for client-side development, and it does include source code to everything
except for the ElevateDB Server.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<< Were you trying to access a
configuration/database directly on the WinCE device ?  And, if so, are you
sure that you didn't have any other processes running that were already
using the same configuration ?>>

Tried it  again.  Started the engine with an empty db directory (wanted to create the
database from code) and  with existing data too. Everything worked under win32 but opening
the session under WinCE  failed - this time  with error #406 - in both cases. As these
test has been done with an outdated early version of the LCL port, there is no point
trying to find why it is not working. It has probably been fixed long ago.  If you can
confirm that ElevateDB LCL  has been T_E_S_T_E_D and  is ready for WinCE developement  I
need to make up my mind  and purchase it. If it has not been throughly tested yet, I am
stucked.


<< Right now the only way to compile the unlimited ElevateDB Server is with Delphi ...>>

My strategy would be to use periodically syncronised  Linux and  Windows servers at
different places with mixed Windows, Linux and WinCE clients, while having only one well
tested source for all platforms. EDB LCL would be the ideal candidate for that, but I am
afraid I may be too early.  I only wish the development of EDB had been started at least a
year earlier.   


Regards, Leslie

<<My strategy would be to use periodically syncronised  Linux and  Windows servers at
different places with mixed Windows, Linux and WinCE clients>>

=

My strategy would be to use periodically syncronised  Linux and  Windows servers at
different locations, each having mixed Windows, Linux and WinCE local clients ...

Leslie,

<< Tried it  again.  Started the engine with an empty db directory (wanted
to create the database from code) and  with existing data too. Everything
worked under win32 but opening the session under WinCE  failed - this time
with error #406 - in both cases. As these test has been done with an
outdated early version of the LCL port, there is no point
trying to find why it is not working. It has probably been fixed long ago.
If you can confirm that ElevateDB LCL  has been T_E_S_T_E_D and  is ready
for WinCE developement  I need to make up my mind  and purchase it. If it
has not been throughly tested yet, I am stucked. >>

Of course it has been tested.  However, I'll double-check this just to make
sure that it is working okay.

<< My strategy would be to use periodically syncronised  Linux and  Windows
servers at different places with mixed Windows, Linux and WinCE clients,
while having only one well tested source for all platforms. EDB LCL would be
the ideal candidate for that, but I am afraid I may be too early.  I only
wish the development of EDB had been started at least a year earlier.  >>

What are you talking about ?  You asked me to provide LCL support for
Windows CE back in *August*.   I promptly did so, and you have done nothing
with it since that point.  I specifically went out of my way for you on
this.

--
Tim Young
Elevate Software
www.elevatesoft.com

Leslie,

<< Tried it  again.  Started the engine with an empty db directory (wanted
to create the database from code) and  with existing data too. Everything
worked under win32 but opening the session under WinCE  failed - this time
with error #406 - in both cases. As these test has been done with an
outdated early version of the LCL port, there is no point trying to find why
it is not working. It has probably been fixed long ago.  If you can confirm
that ElevateDB LCL  has been T_E_S_T_E_D and  is ready for WinCE
developement  I need to make up my mind  and purchase it. If it has not been
throughly tested yet, I am stucked. >>

I just tested this again with 2.02 B7 and it works just fine.  I created a
sample WinCE application that accesses a local database using the Windows
Mobile 6 Professional Emulator.

I'll be doing a new technical article on creating a Windows CE application
with Lazarus this week, so perhaps that will help you get everything set up
properly.

--
Tim Young
Elevate Software
www.elevatesoft.com

Looking forward the article.

Leslie

Leslie,

<< Looking forward the article. >>

The article should be ready by next week, but here's a look at the sample
application:

http://www.elevatesoft.com/shoplistwince.png

It's compiled using Lazarus 0.926 and uses data-aware controls.  However,
it's also 4Mb in size.  But, something like KOL-CE would trim a lot of the
fat off, in exchange for losing the data-aware controls:

http://wiki.freepascal.org/KOL-CE

BTW, I suspect that you're issue with running under WinCE with ElevateDB is
that you're trying to execute the application from the \Storage Card on the
emulator.  Locking does not work properly under WinCE when you do so, at
least with the emulator.  You have to run the application directly on the
device storage.  For example, with the sample application above, I'm running
it from the \Shopping directory off the root.

--
Tim Young
Elevate Software
www.elevatesoft.com