Hi

I am writing this email to make a reflection about the timing of the releases of ElevateSoft

I am a very happy customer of dbisam and EDB, for many years, this is not a complaint but just a friendly discussion , about how the Delphi world has changed lately.

I use many Delphi components ( DevExpress , ReportBuilder , TMS , EDB ... ) ,  when Embarcadero released  Delphi XE3, within a month ( TMS days... , other week )  all the partner above, released (even with minor releases ) their component including the support to the new compiler ,

In the last years, ElevateSoft has been the last that release their updated components.

Every time we had to wait , wait  , wait  the migration to the new IDE for the lack of updated components for DBISAM / EDB .

We do not update the IDE for hobby, we are developing using Delphi Mobile / DataSnap applications ... and having the last version of Delphi IDE is mandatory.

Now ....

Embarcadero has increased their update cycle, reducing it to 6 months and today, with XE6, we find ourself in the same situation of always, Everyonel except Elevate have released any update.


We ask Tim to reconsider its allocation of priority , to come closer to its clients , I asked often Tim , the Beta of EDB , ( enough that compiling ), but the response has always been negative .

I understand that other products asking for his attention, but I would like to ask that the upgrade to the new compilers will be managed with greater importance and with lesser waiting .


i would like to remember that the difficulties of the migration from XE5 to XE6 are almost nothing.


Best Regards

Mauro Botta

On 5/12/2014 8:52 AM, Mauro Botta wrote:
> We ask Tim to reconsider its allocation of priority , to come closer to its clients , I asked often Tim , the Beta of EDB , ( enough that compiling ), but the response has always been negative .

EDB and DBISAM can both be bought in source code form and recompiled by
you so that option has always been available.  I'm guessing this is the
reason beta does not really make sense.


Raul

Mauro


If Raul hadn't beaten me to it I was going to suggest recompiling it yourself.

I'm also slightly baffled. I can understand you wanting the latest IDE for mobile development, but as far as I know ElevateDB doesn't run on a mobile platform apart from a Surface Pro. My simple take on it is that all you'll be doing is interacting with a server running on Windows server somewhere so I don't understand the urgency.

Roy Lambert

On 12/05/2014 10:52 PM, Mauro Botta wrote:
> Hi
>
> I am writing this email to make a reflection about the timing of the releases of ElevateSoft

Mauro and others,

I too have been using DBISAM for many years. I am now switching, but
have not switched to, ElevateDB until the moment I release my products.

The problem is in switching to ElevateDB. My intention is to recompile
in Delphi XE6. Then send out my products to my Beta testers.
Unfortunately I can not do this until ElevateDB for Delphi XE6 is released.

Currently I pay maintenance for DBISAM and ElevateDB. It was my
understanding that maintenance enables the vendor to bring out timely
updates for new compiler versions.

You are right about "the Delphi world has changed lately". It has
changed with the increased tempo of Delphi releases, and the
encompassing of mobile devices.

I too use many Delphi components, such as TMS Software. I have a 3 page
list of components/software that I use. I am only waiting on two other
vendors : Precision; Addictive Software. For the Addict Spell Checker I
am only waiting for receipt of the changes that have already been
made for Delphi XE6. Should arrive today?

But those vendor's code is not important right now. I need ElevateDB.

You say "we are developing using Delphi Mobile / DataSnap applications
and having the last version of Delphi IDE is mandatory". That
statement is correct. Watching live how Marco Cantu (and another
Embarcadero person) demonstrated DataSnap it is essential to have
the ElevateDB components for your compiler. You create your program
"parts" in a Project Group. One part is FireMonkey, another the
server, another the shared Delphi units. This is the way an associate of
mine also develops with DataSnap and has released a product to Android.

In the last 24 hours TMS Software has released a new product. A
challenger to DataSnap? Regardless, that product works with
ElevateDb. This is another reason to get out the Delphi XE6 update for
ElevateDB.

Regards,
  Peter Evans

And here we are again with the usual problems.

XE7 is available from 17 days from Elevate no information about the timing or anything.

I changed my license DBISAM, from STD to STD with sources, but not all the sources are released (I guess for problems to manage their license)


I can not spend $ 719 for the version C / S Full Src, (I do not need dbisam-server) just to be able to recompile dbisam because of their slowness, no beta support, no info....

Mauro Botta wrote:

> I changed my license DBISAM, from STD to STD with sources, but not
> all the sources are released (I guess for problems to manage their
> license)

Are you getting an error when building? Someone posted the other day
with an error, but a simple definition would solve it. Perhaps if you
ask a specific issue you could get more help?


--

Matthew Jones

Matthew Jones wrote:

> Someone posted the other day
> with an error, but a simple definition would solve it.

D'oh! I see it was you! Did you try the definition? It appears that it
isn't hard to make it work - probably the usual modify the overall INC
to handle the VER___ value, and then it should compile.

--

Matthew Jones

i have dbisam with source license and i have xe6 source but any dbisam-server units are missing , only .dcu ( xe6 )

i don't use dbisam server.

Mauro Botta wrote:

>
> i have dbisam with source license and i have xe6 source but any
> dbisam-server units are missing , only .dcu ( xe6 )

So what error are you seeing? You said previously:


{$IFNDEF DBISAM_NOSERVER}
dbisamsv,
{$ENDIF}


[dcc32 Fatal Error] dbisamen.pas(3602): F1026 File not found:
'V:\xxxxxxxxxxxxxx\DBISAM_Win32\code\source\dbisamsv.dcu'

The obvious solution is therefore to add a preprocessor definition in
the project of DBISAM_NOSERVER and it will then ignore the unit and you
can continue.

Perhaps best pick this up in the dbisam newsgroup?

--

Matthew Jones