1. One more time: RDMS for DOS and Windows
After all the comotion no one has yet clearly pointed to me which direction
I should be going. Again my concern is that I need a RDBMS that would work
with Euphoria for both DOS and and Windows. I still have applications
running on 386 and 486 machines written in clipper. I want to upgrade
and/or ehance the features of these legacy applications using Euphoria.
Regards,
Arlie Codina
2. Re: One more time: RDMS for DOS and Windows
On Fri, 25 Feb 2000 17:50:15 -0500, Arlie Codina <eu at FLASHMAIL.COM> wrote:
>After all the comotion no one has yet clearly pointed to me which direction
>I should be going. Again my concern is that I need a RDBMS that would work
>with Euphoria for both DOS and and Windows. I still have applications
>running on 386 and 486 machines written in clipper. I want to upgrade
>and/or ehance the features of these legacy applications using Euphoria.
Arlie:
Can you call or send commands from another application to your DOS
version of Clipper. If you can then you could write a more friendly
and better looking front-end to your DOS applications. This would aid
you in getting your customers use to a GUI type interface and give
you some experience with Euphoria. In a addition you maybe able to
use the front-end across different platforms. This also would allow
you maybe gain enough familiarity with Euphoria to consider writing
or assisting others on the list in writing a Euphoria data base.
Bernie
3. Re: One more time: RDMS for DOS and Windows
- Posted by Irv Mullins <irv at ELLIJAY.COM>
Feb 25, 2000
-
Last edited Feb 26, 2000
From: Arlie Codina <eu at FLASHMAIL.COM>
> After all the comotion no one has yet clearly pointed to me which
direction
> I should be going. Again my concern is that I need a RDBMS that would work
> with Euphoria for both DOS and and Windows. I still have applications
> running on 386 and 486 machines written in clipper. I want to upgrade
> and/or ehance the features of these legacy applications using Euphoria.
Arlie:
You have received several workable suggestions from people who do this
kind of work daily. Unfortunately, none of them meet all your criteria,
and frankly I don't think you will ever find one which does.
A relational database engine is not the kind of thing people write for fun.
No one is likely to develop a new one for DOS, much less one which is
open, 32-bit, and callable from Euphoria.
Therefore, the choices which remain are:
1. To write your own Euphoria routines to access your existing data.
Daniel Berstein's dbase III code would be a good starting point.
One (of many) problems: you will have to implement your own record locking.
2. To buy more memory for your server, and install mysql. Fabio's Euphoria
mysql wrapper will work with that. The drawback is that the server, at
least,
will have to run Windows in order to use the dll.
3. To forget about Euphoria for database work, and use a clipper clone such
as
Flagship. Most of these are only available for Linux, not for DOS, for good
reasons. Luckily, Linux will run acceptably fast on 386 pc's. Again, you'll
need more memory.
4. To use Kat's soon-to-be-released code (let's hope it's multi-user)
5. To stay with Clipper.
Regards,
Irv
4. Re: One more time: RDMS for DOS and Windows
> and frankly I don't think you will ever find one which does.
>
> A relational database engine is not the kind of thing people write for
> fun.
> No one is likely to develop a new one for DOS, much less one which is
> open, 32-bit, and callable from Euphoria.
>
> Therefore, the choices which remain are:
>
> 1. To write your own Euphoria routines to access your existing data.
> Daniel Berstein's dbase III code would be a good starting point.
> One (of many) problems: you will have to implement your own record
> locking.
Some time ago, I sent to the RDS archives a little program that shows how
to lock records across a network; Maybe it can help. ( LOCK / RLOCK )
Greets
Hugo
5. Re: One more time: RDMS for DOS and Windows
- Posted by Joel Crook <joel at MAIL.K-A.COM>
Feb 26, 2000
-
Last edited Feb 27, 2000
--=====================_4354930==_.ALT
Clipper is essentially an xbase application and xbase is the same as DBase. So
you might look at the dbf access routines in the RDS archives. There are
differences to the languages introduced to Clipper after CA bought the product.
Which version are you dealing with? The reason I ask that question is to help
you determine how different then dbf files you've got are from the xbase format
in terms of the fields and indexing.
As you can see from the discussion there is no agreement as to what a database
should include but the dbf_eng.zip in the RDS archive (at least according to
the docs) will read and write dBase files. There is a dBase field description
included as well. So that can get you started but it appears you get the fun
task of finishing building a dbf library: sorting, hashing, calculating,
indexing and reindexing not to mention networking the whole thing. At least the
file i/o part is done.
For shear economy of effort I don't suggest you immediately change from xbase
to SQL or any other format just yet until you have your feet grounded in
Euphoria and its strengths and weaknesses.
a clipper faq:
good luck and regards,
At 05:50 PM 02/25/2000 -0500, you wrote:
>After all the comotion no one has yet clearly pointed to me which direction
>I should be going. Again my concern is that I need a RDBMS that would work
>with Euphoria for both DOS and and Windows. I still have applications
>running on 386 and 486 machines written in clipper. I want to upgrade
>and/or ehance the features of these legacy applications using Euphoria.
>
>Regards,
>Arlie Codina
Joel H. Crook
"A Strong house is built upon a strong foundation. What are your beliefs built
upon?"
-- "The Book of Reminders"
--=====================_4354930==_.ALT
<html><div>Clipper is essentially an xbase application and xbase is the
same as DBase. So you might look at the dbf access routines in the RDS
archives. There are differences to the languages introduced to Clipper
after CA bought the product. Which version are you dealing with? The
reason I ask that question is to help you determine how different then
dbf files you've got are from the xbase format in terms of the fields and
indexing.</div>
<br>
<div> As you can see from the discussion there is no agreement as to
what a database should include but the dbf_eng.zip in the RDS archive (at
least according to the docs) will read and write dBase files. There
is a dBase field description included as well. So that can get you
started but it appears you get the fun task of finishing building a dbf
library: sorting, hashing, calculating, indexing and reindexing not to
mention networking the whole thing. At least the file i/o part is
done.</div>
<br>
<div>For shear economy of effort I don't suggest you immediately change
from xbase to SQL or any other format just yet until you have your feet
grounded in Euphoria and its strengths and weaknesses.</div>
<br>
<div>a clipper faq:</div>
<div><a href="http://www.hagbard.demon.co.uk/clipper-faq/clipper.html"
EUDORA=AUTOURL>http://www.hagbard.demon.co.uk/clipper-faq/clipper.html</a></div>
<br>
<br>
<div>good luck and regards, </div>
<br>
<br>
<br>
<div>At 05:50 PM 02/25/2000 -0500, you wrote:</div>
<div>>After all the comotion no one has yet clearly pointed to me
which direction</div>
<div>>I should be going. Again my concern is that I need a RDBMS that
would work</div>
<div>>with Euphoria for both DOS and and Windows. I still have
applications</div>
<div>>running on 386 and 486 machines written in clipper. I want to
upgrade</div>
<div>>and/or ehance the features of these legacy applications using
Euphoria.</div>
<div>></div>
<div>>Regards,</div>
<div>>Arlie Codina</div>
<br>
Joel H. Crook<br>
<br>
"<b><i>A Strong house is built upon a strong foundation. What are
your beliefs built upon</b></i>?"<br>
<div align="right">
-- "The Book of Reminders"</html>
--=====================_4354930==_.ALT--
