Hi,
it's possible to use unicode in ElevateDB in C++ personality of BDS 2006?

thanks!

<< it's possible to use unicode in ElevateDB in C++ personality of BDS 2006?
>>

Yep, I was just waiting for any requests to do so. I will see about
getting this in the next build.

--
Tim Young
Elevate Software
www.elevatesoft.com

> Yep, I was just waiting for any requests to do so.

Hmmm... in *that* case

When's the Kylix/Linux version coming out?  If I recall correctly, it
was "expected" "2 weeks" after the initial release of EDB (back in
Feb.? Valentines?)... (I'm so late on my own projects that that delay
didn't even hurt! But I'm gonna need it soon. He says confidently...)

Though... I am confused about whether it's really out already. I don't
see it on the Order page (expecting to see CLX ID codes), but several
other locations describe it as currently available. For example: On
http://www.elevatesoft.com/prodinfo.htm it says:
   (IS AVAILABLE emphasis mine)

> ElevateDB is our latest embedded database engine for use by
developers > within their applications. It IS AVAILABLE for the Borland
Delphi,
> C++Builder, Kylix, Developer Studio, and .NET development
> environments, as well as for any development environment that can use
> ODBC for data access.


Coud that mean it's just *one* product? Doesn't seem likely, nor do the
Order Page descriptions imply that. Chances are, it's the proverbial
"is available" seen more often these days when delivery falls
behind intentions. [Don't mind (exhausted) me, I'm singing my own tale
of woe. Man I can't WAIT to ship!!! And face all those expectant users
.. (or was that expectorating users?)]


P.S. Sorry, but what does the "DAC" Product ID code stand for?  Can't
seem to find an explanation, and none are coming to mind.

Very good thanks!


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> ha scritto nel
messaggio news:39A14CD7-5023-441D-92F8-B0FD0FABF0FE@news.elevatesoft.com...
> << it's possible to use unicode in ElevateDB in C++ personality of BDS
> 2006?
> >>
>
> Yep, I was just waiting for any requests to do so. I will see about
> getting this in the next build.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

>
> P.S. Sorry, but what does the "DAC" Product ID code stand for?  Can't
> seem to find an explanation, and none are coming to mind.

DAC stands for "Data Access Components"

.... EDB-DAC (Data Access Components) line of ElevateDB products...
(Taken from the front page of www.ElevateSoft.com)

Chris Holland

John,

<< When's the Kylix/Linux version coming out?  If I recall correctly, it was
"expected" "2 weeks" after the initial release of EDB (back in Feb.?
Valentines?)... (I'm so late on my own projects that that delay didn't even
hurt! But I'm gonna need it soon. He says confidently...) >>

I'm revisiting the Kylix support at this point since Kylix simply won't work
with a lot of the new distributions.  In fact, I simply couldn't get it to
work at all with OpenSuse.  It may mean a port to FreePascal instead.

<< Though... I am confused about whether it's really out already. I don't
see it on the Order page (expecting to see CLX ID codes), but several other
locations describe it as currently available. For example: On
http://www.elevatesoft.com/prodinfo.htm it says:
(IS AVAILABLE emphasis mine) >>

I'll modify that.

<< P.S. Sorry, but what does the "DAC" Product ID code stand for?  Can't
seem to find an explanation, and none are coming to mind. >>

Data Access Components - basically everything that is CLI-compliant or close
like the ODBC driver .NET data provider, etc.

--
Tim Young
Elevate Software
www.elevatesoft.com

Chris,

Thanks for answering the natural interpretation of the question I
wrote, but that wasn't exactly what I meant.

> DAC stands for "Data Access Components"

I don't understand what DAC *or* "Data Access Components" means. Here's
what I (and newcomers...) see, when coming to the site (from the point
of view of someone who's been using other environments and terminology
for quite a while):

As you point out, DAC is "highlighted" on the front page. Hmmm... Data
Access Components... pretty much sounds like a name encompassing the
gist all of Elevate's products. Wonder what that is? Sounds like it
belongs on a VERY particular page of the Component Palette. So far,
we know it's a "line of products,"  and that there's a migration path
to it, so it's "upgradable."


Let's follow the link. That takes us to an order page with a list of
Product IDs, short Descriptions, and Prices. Here, we discover that
"DAC" forms part of the Product IDs, like VCL and the missing CLX, so
does it refer to the use of a particular library (or "partial
environment")?  Not likely.


From further investigation (using Google to peer more effectively into
ElevateSoft.com), it looks like this is a DAC, as in MS's MDAC.

Which seems even more confusing with the Product ID scheme. Isn't this
then a set of drivers and/or providers? Why would the products be
segmented by "programming library/environment" (VCL vs. CLX) and
providers, yet the DAC descriptions sound close to the VCL and CLX
products...?    I'm SO confused ..

Tim,

> I'm revisiting the Kylix support at this point since Kylix simply
> won't work with a lot of the new distributions.

HOLY $!@#$%^&*(  !!!!!

A bunch of us have been waiting about 2 years for this!
(http://www.elevatesoft.com/scripts/newsgrp.dll?action=openmsg&group=15&
msg=47&page=1  and
http://www.elevatesoft.com/scripts/newsgrp.dll?action=openmsg&group=3&ms
g=1645&page=1 ) Repeatedly checking the website for status updates.
Trying to read "between the lines," I had been guesstimating/hoping
that you'd release Kylix/Linux support right after 1.06...

You asked me back in January or February if I'd be willing to work with
the Kylix version (on this newsgroup somewhere I think...). I should
have answered YES immediately!!  But I'm swamped with other stuff, as
already bemoaned in this thread.  I may change that answer to YES VERY
SOON THOUGH. Give me a day or so to contemplate exactly how nuts I am.
If you think another motivated developer's involvement (my efforts,
that is) could influence your decision on Kylix support, that could
influence my decision and all-in-all get very recursive...  please
mention it...  Though maybe you want feedback from other Kylix users
first...

EVEN MORE IMPORTANTLY THOUGH: (Whew!) That statement of yours quoted
above isn't actually true, though you have to jump through 73 hoops
reciting the right incantations during the auspicious phases of the
moon, dressed like a Druid, to discover it. There are a number of
geniuses out there that discovered AND FIXED the major problems. (They
even involved some Linux kernel developers at points.) And it works
beautifully once you apply those fixes (and mess with the environment
like preventing KDE "focus stealing" etc.)

I've been intending to document all the steps I needed to perform
(which were not exactly what I found in the posted instructions,
perhaps due to a different distro), so that I could set up any new
replacement machine without taking weeks of research again, but it kept
slipping down the priority list. Methinks it just got bumped up a few
notches.  The docs out on the web already are enough for a motivated
developer to get things running, but I also wanted to make sure I'd
have an updated set in case those instructions disappear.

Quite a few people gave up on Kylix because of those problems, but with
the wider dissemination of that information (perhaps even on your
site), and active support from tools like yours and libraries like
TDBF, Synapse, and others, I wouldn't be surprised at a significant
resurgence.


Well... I was exhausted after a few very rough days, but since I
probably won't get to sleep after this news... maybe I should go check
on those Kylix instructions now <weary grin>...


Hmmm... some quick results inserted here right away:

http://www.danielbautista.com/articulos/install_kylix.html

If I remember correctly, that page didn't help that much. But I'll need
to revisit it. It's been way too long.

Hmmm... Wonderful. The Borland pages for "How To run Kylix on a 2.6.x
Linux kernel" have disappeared now along with the other support
elements. But that was a short and not-that-wonderful entry anyway,
whose information was duplicated in numerous other places.

Ahah! Here are the important pages (I'm pretty sure):
 http://www.codecomments.com/archive398-2006-3-811546.html
and ESPECIALLY
 http://www.theo.ch/kylix/suse10.html
which refers to the ptrace code in the above link anyway.


Ughhhh... I need to get my mind off this now. I guess it's "back to our
regularly scheduled programming" as a nightcap now... I'll definitely
be back tomorrow.

Tim,

Just a quick aside: It looks like your server's clock may be running
about 5 minutes fast. Among numerous possibilities: Depending on the OS
you're using, you may be counting on Windows periodically synchronizing
its time... That had a few hiccups earlier this year, and several of
the time servers, including that of MS and NIST.gov, were/are no longer
supplying time via the old protocol MS is/was using. If that's the case
here, switching to another (gov) time server will do the trick...

John,

<< I don't understand what DAC *or* "Data Access Components" means. Here's
what I (and newcomers...) see, when coming to the site (from the point of
view of someone who's been using other environments and terminology
for quite a while): >>

Data Access Components is a catch-all that encompasses all of the MS data
access technologies.  We don't use MDAC because of the fact that it will
also include the Linux ODBC driver at some point.

--
Tim Young
Elevate Software
www.elevatesoft.com