Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 10 of 10 total
Thread A general-purpose front end to access DBISAM database server
Wed, Jan 25 2006 11:32 AMPermanent Link

I have a customer who has used Paradox for years to access data in Paradox
files on his local machine.  His business has increased from a one man band
working from home to a three person outfit, each of them working from home.

At present, they overcome the geographical separation by each having their
own copy of the database.  When one of them makes changes to a record on the
database, they mark the record with their initials and date.  At the end of
the day they query out the records they have changed that day and email them
to each other!  EEK!

I have been looking into setting up a database server and getting the three
of them to access live data.  

I set up a DBISAM server on his machine, and installed a DBISAM ODBC driver
on one of the client machines so that Paradox can see the live data,
accessing the data over the Internet with broadband at each end.

Scrolling down through the data in Paradox, with the grid showing 38 records,
it takes 18 to 28 seconds per page to page down through the data.

Using the Database system Utility, with the grid showing 38 records, it takes
6 to 15 seconds per page to page down through the data.

So that is in the same ball park.  I maybe could improve things by tweaking
the read-ahead for the ODBC driver.

However, when I use the locate feature of Paradox to find a particular record
using the field that is the primary index for the table, I can go and have
lunch before the screen updates, if the record is a fair way into the table.  
Paradox appears to be reading every record from the database server and
checking it to see if it matches.

We can't live with something that slow, so my questions are:-

1. Can I get round the problem with Paradox?

2. What other database front-ends are available that make more intelligent
database accesses?

I could write him an application in Delphi, but he is used to being able to
access his data "in the raw" and do whatever he likes with it.  Tying him
down to a spec for writing the software would be difficult.

Any suggestions?

--Bill Sparrow--
Wed, Jan 25 2006 1:34 PMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Bill


Why not let them continue to suffering. Install Terminal Services and keep on running Paradox Smiley

dbi Desktop is better than DBSys but I doubt that it would be up to the task if they're using much of Paradox's capabilities.

Roy Lambert
Wed, Jan 25 2006 2:58 PMPermanent Link

Jon Lloyd Duerdoth
Bill,

I'm dabbling with MySQL right now for a similar reason.
How to handle reports etc is an issue without some sort
of application. Accessing using Paradox would probably not
be suitable (or fast).

Jon

bsparrow@cix.co.uk (Bill Sparrow) wrote:
> I have a customer who has used Paradox for years to access data in Paradox
> files on his local machine.  His business has increased from a one man band
> working from home to a three person outfit, each of them working from home.
>
> At present, they overcome the geographical separation by each having their
> own copy of the database.  When one of them makes changes to a record on the
> database, they mark the record with their initials and date.  At the end of
> the day they query out the records they have changed that day and email them
> to each other!  EEK!
>
> I have been looking into setting up a database server and getting the three
> of them to access live data.  
>
> I set up a DBISAM server on his machine, and installed a DBISAM ODBC driver
> on one of the client machines so that Paradox can see the live data,
> accessing the data over the Internet with broadband at each end.
>
> Scrolling down through the data in Paradox, with the grid showing 38 records,
> it takes 18 to 28 seconds per page to page down through the data.
>
> Using the Database system Utility, with the grid showing 38 records, it takes
> 6 to 15 seconds per page to page down through the data.
>
> So that is in the same ball park.  I maybe could improve things by tweaking
> the read-ahead for the ODBC driver.
>
> However, when I use the locate feature of Paradox to find a particular record
> using the field that is the primary index for the table, I can go and have
> lunch before the screen updates, if the record is a fair way into the table.  
> Paradox appears to be reading every record from the database server and
> checking it to see if it matches.
>
> We can't live with something that slow, so my questions are:-
>
> 1. Can I get round the problem with Paradox?
>
> 2. What other database front-ends are available that make more intelligent
> database accesses?
>
> I could write him an application in Delphi, but he is used to being able to
> access his data "in the raw" and do whatever he likes with it.  Tying him
> down to a spec for writing the software would be difficult.
>
> Any suggestions?
>
> --Bill Sparrow--
>
Wed, Jan 25 2006 4:35 PMPermanent Link

Michael Baytalsky

For My SQL there's a tool called DBTools. And plenty of other
great tools. http://www.dbtools.com.br/
But it's more like database manager, not a complete front-end
per se.

Regards,
Michael

Jon Lloyd Duerdoth wrote:
> Bill,
>
> I'm dabbling with MySQL right now for a similar reason.
> How to handle reports etc is an issue without some sort
> of application. Accessing using Paradox would probably not
> be suitable (or fast).
>
> Jon
>
> bsparrow@cix.co.uk (Bill Sparrow) wrote:
>> I have a customer who has used Paradox for years to access data in
>> Paradox files on his local machine.  His business has increased from a
>> one man band working from home to a three person outfit, each of them
>> working from home.
>>
>> At present, they overcome the geographical separation by each having
>> their own copy of the database.  When one of them makes changes to a
>> record on the database, they mark the record with their initials and
>> date.  At the end of the day they query out the records they have
>> changed that day and email them to each other!  EEK!
>>
>> I have been looking into setting up a database server and getting the
>> three of them to access live data.
>> I set up a DBISAM server on his machine, and installed a DBISAM ODBC
>> driver on one of the client machines so that Paradox can see the live
>> data, accessing the data over the Internet with broadband at each end.
>>
>> Scrolling down through the data in Paradox, with the grid showing 38
>> records, it takes 18 to 28 seconds per page to page down through the
>> data.
>>
>> Using the Database system Utility, with the grid showing 38 records,
>> it takes 6 to 15 seconds per page to page down through the data.
>>
>> So that is in the same ball park.  I maybe could improve things by
>> tweaking the read-ahead for the ODBC driver.
>>
>> However, when I use the locate feature of Paradox to find a particular
>> record using the field that is the primary index for the table, I can
>> go and have lunch before the screen updates, if the record is a fair
>> way into the table.  Paradox appears to be reading every record from
>> the database server and checking it to see if it matches.
>>
>> We can't live with something that slow, so my questions are:-
>>
>> 1. Can I get round the problem with Paradox?
>>
>> 2. What other database front-ends are available that make more
>> intelligent database accesses?
>>
>> I could write him an application in Delphi, but he is used to being
>> able to access his data "in the raw" and do whatever he likes with
>> it.  Tying him down to a spec for writing the software would be
>> difficult.
>>
>> Any suggestions?
>>
>> --Bill Sparrow--
>>
Wed, Jan 25 2006 10:22 PMPermanent Link

Jon Lloyd Duerdoth
Thanks Michael

Right now I've got a mix of DBISAM and MySQL... kind of an interesting
hybrid Smile

Jon

Michael Baytalsky wrote:
>
> For My SQL there's a tool called DBTools. And plenty of other
> great tools. http://www.dbtools.com.br/
> But it's more like database manager, not a complete front-end
> per se.
>
> Regards,
> Michael
>
> Jon Lloyd Duerdoth wrote:
>> Bill,
>>
>> I'm dabbling with MySQL right now for a similar reason.
>> How to handle reports etc is an issue without some sort
>> of application. Accessing using Paradox would probably not
>> be suitable (or fast).
>>
>> Jon
Thu, Jan 26 2006 5:21 AMPermanent Link

Ah, now there's a thought.  He tends to use low end kit.  What would be the
minimum spec needed to run Terminal Services to support one or two users at a
time?

He has a machine running XP Pro.  I guess I could set it up to allow Remote
Desktop access as a "proof of concept"?

--Bill Sparrow--


In article <6EE684E8-F0CF-4763-AF5E-602652DCB043@news.elevatesoft.com>,
roy.lambert@skynet.co.uk (Roy Lambert) wrote:

> *Subject:* Re: A general-purpose front end to access DBISAM database server
> *From:* Roy Lambert <roy.lambert@skynet.co.uk>
> *Date:* Wed, 25 Jan 2006 18:34:03 +0000
>
> Bill
>
>
> Why not let them continue to suffering. Install Terminal Services and keep
on running Paradox Smiley
>
> dbi Desktop is better than DBSys but I doubt that it would be up to the
task if they're using much of Paradox's capabilities.
>
> Roy Lambert
>
>
Thu, Jan 26 2006 5:56 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Bill


In theory you need a "proper" server, but with light use a new pc with 1Gb RAM and a 3Ghz cpu ought to be ok.

Roy Lambert
Thu, Jan 26 2006 8:28 AMPermanent Link

Michael Baytalsky

I've been actually thinking about building a generic
front-end for any database which would include, edit and
browse forms, reports, database designer, diagramming, etc.
Most of it I already have in components, including
generic database adapters. Maybe eventually I will
build it...

Regards,
Michael

Jon Lloyd Duerdoth wrote:
> Thanks Michael
>
> Right now I've got a mix of DBISAM and MySQL... kind of an interesting
> hybrid Smile
>
> Jon
>
> Michael Baytalsky wrote:
>>
>> For My SQL there's a tool called DBTools. And plenty of other
>> great tools. http://www.dbtools.com.br/
>> But it's more like database manager, not a complete front-end
>> per se.
>>
>> Regards,
>> Michael
>>
>> Jon Lloyd Duerdoth wrote:
>>> Bill,
>>>
>>> I'm dabbling with MySQL right now for a similar reason.
>>> How to handle reports etc is an issue without some sort
>>> of application. Accessing using Paradox would probably not
>>> be suitable (or fast).
>>>
>>> Jon
Thu, Jan 26 2006 8:34 AMPermanent Link

I think I'd look at doing some sort of basic Delphi app with a local
database and a grid and reporting system to echo Paradox, and have them
upload changes to a central PC occasionally. This could be done using
something as simple as RemObjects, or perhaps even connecting to the
client server DBISAM directly.

You might find that you can then get them to start specifying what they do
with it, so you can customise it better.

/Matthew Jones/ (also on CIX!)
Thu, Jan 26 2006 9:01 AMPermanent Link

"R. Tipton"
I think maybe a replication tool would do the trick if there
are any for Paradox that is something like copycat.
http://www.microtec.fr/copycat/ct/
(tip websearch paradox replication tool)
It would be nice in Dbisam as well.
Rita

"Bill Sparrow" <bsparrow@cix.co.uk> wrote in message
news:memo.20060125163248.348A@bsparrow.uwclub.net...
>I have a customer who has used Paradox for years to access data in Paradox
> files on his local machine.  His business has increased from a one man
> band
> working from home to a three person outfit, each of them working from
> home.
>
> At present, they overcome the geographical separation by each having their
> own copy of the database.  When one of them makes changes to a record on
> the
> database, they mark the record with their initials and date.  At the end
> of
> the day they query out the records they have changed that day and email
> them
> to each other!  EEK!
>
> I have been looking into setting up a database server and getting the
> three
> of them to access live data.
>
> I set up a DBISAM server on his machine, and installed a DBISAM ODBC
> driver
> on one of the client machines so that Paradox can see the live data,
> accessing the data over the Internet with broadband at each end.
>
> Scrolling down through the data in Paradox, with the grid showing 38
> records,
> it takes 18 to 28 seconds per page to page down through the data.
>
> Using the Database system Utility, with the grid showing 38 records, it
> takes
> 6 to 15 seconds per page to page down through the data.
>
> So that is in the same ball park.  I maybe could improve things by
> tweaking
> the read-ahead for the ODBC driver.
>
> However, when I use the locate feature of Paradox to find a particular
> record
> using the field that is the primary index for the table, I can go and have
> lunch before the screen updates, if the record is a fair way into the
> table.
> Paradox appears to be reading every record from the database server and
> checking it to see if it matches.
>
> We can't live with something that slow, so my questions are:-
>
> 1. Can I get round the problem with Paradox?
>
> 2. What other database front-ends are available that make more intelligent
> database accesses?
>
> I could write him an application in Delphi, but he is used to being able
> to
> access his data "in the raw" and do whatever he likes with it.  Tying him
> down to a spec for writing the software would be difficult.
>
> Any suggestions?
>
> --Bill Sparrow--
>

Image